Re: Memory leak (possibly connected to postgis) leading to server crash

From: Roman Cervenak <roman(at)cervenak(dot)info>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Memory leak (possibly connected to postgis) leading to server crash
Date: 2019-12-11 17:23:39
Message-ID: CAGjExY2oYp162GVi-gdQ4s0++3BQnT3Kyqnq3WmAKJy9H_WNdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Same error with call.

On Wed, Dec 11, 2019, 17:49 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Roman Cervenak <roman(at)cervenak(dot)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
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2019-12-11 17:40:11 Re: logical replication: could not create file "state.tmp": File exists
Previous Message Andres Freund 2019-12-11 17:21:01 Re: logical decoding bug: segfault in ReorderBufferToastReplace()