Postgres Pro
Downloads
Home   >   mailing lists

Re: Memory leak (possibly connected to postgis) leading to server crash - Mailing list pgsql-bugs

From Roman Cervenak
Subject Re: Memory leak (possibly connected to postgis) leading to server crash
Date
Msg-id CAGjExY2oYp162GVi-gdQ4s0++3BQnT3Kyqnq3WmAKJy9H_WNdw@mail.gmail.com
Whole thread Raw
In response to Re: Memory leak (possibly connected to postgis) leading to server crash  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view
Same error with call. 

On Wed, Dec 11, 2019, 17:49 Tom Lane <tgl@sss.pgh.pa.us> wrote:
Roman Cervenak <roman@cervenak.info> writes:
> I am trying to do
> (gdb) p MemoryContextStats(TopMemoryContext)

I think what you wanted to do is "call MemoryContextStats(TopMemoryContext)".
"p" means "print".

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: logical decoding bug: segfault in ReorderBufferToastReplace()
Next
From: Andres Freund
Date:
Subject: Re: logical replication: could not create file "state.tmp": Fileexists