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 CAGjExY2xQa8hxEYBTDDv6Y66V2=D0HEDsmLt42ZVupC3BxsLsQ@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>)
Responses Re: Memory leak (possibly connected to postgis) leading to servercrash  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-bugs
Tree view
With "postgresql-12-dbgsym" installed, call MemoryContextStats(TopMemoryContext) succeeded on postgres backend process with high memory consumption. 
I cut it from server logs, see attached file (I have redacted queries and table structures, I left SELECT parts where is visible that geometric operations are involved).

Regards,
Roman Cervenak

On Wed, Dec 11, 2019 at 5:49 PM 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
Attachment

pgsql-bugs by date:

Previous
From: Manuel Rigger
Date:
Subject: Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c",Line: 89)
Next
From: Tomas Vondra
Date:
Subject: Re: Memory leak (possibly connected to postgis) leading to servercrash