pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Roman Cervenak <roman@cervenak.info>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leak (possibly connected to postgis) leading to server crash
Date: Wed, 11 Dec 2019 15:23:10 +0100
Message-ID: <20191211142310.f5qqzsgxkwt64j42@development> (raw)
In-Reply-To: <CAGjExY0Kb0-h3MqWbiYry3e40nKbYyOW3-=BO7iKLJpo8R66aw@mail.gmail.com>
References: <CAGjExY1C40d=cqbf6nfeNDCLWk57MhFu3mgR0+KRPb8+_uW_KA@mail.gmail.com>
	<20191206110154.v7yshqsn32zyxx4q@development>
	<CAGjExY0sFbx+JytMkY-h8=NWqD_f0DOwB8QXrQ4SqJ+BttoX6g@mail.gmail.com>
	<20191206124119.qe2xaffcbkcbmve3@development>
	<CAGjExY0Kb0-h3MqWbiYry3e40nKbYyOW3-=BO7iKLJpo8R66aw@mail.gmail.com>

Hi,

On Wed, Dec 11, 2019 at 12:09:11PM +0100, Roman Cervenak wrote:
>Hi,
>I am trying to do
>
>(gdb) p MemoryContextStats(TopMemoryContext)
>
>on postgres backend process, but the response is: 'TopMemoryContext' has
>unknown type; cast it to its declared type
>
>I never debugged postgres (or anything under linux), and google is not
>helpful. Can you please advise? Full output is attached.
>

Hmmmm, I don't recall having this issue. Can you try installing the
package with debug symbols, it should be called -debug or so.


regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (16+ messages)  latest in thread

Message-ID: <20191211142310.f5qqzsgxkwt64j42@development>
Permalink:  ../20191211142310.f5qqzsgxkwt64j42@development/
Also on:    postgresql.org/message-id/20191211142310.f5qqzsgxkwt64j42@development

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, roman@cervenak.info
  Subject: Re: Memory leak (possibly connected to postgis) leading to server crash
  In-Reply-To: <20191211142310.f5qqzsgxkwt64j42@development>
  References: <CAGjExY1C40d=cqbf6nfeNDCLWk57MhFu3mgR0+KRPb8+_uW_KA@mail.gmail.com> <20191206110154.v7yshqsn32zyxx4q@development> <CAGjExY0sFbx+JytMkY-h8=NWqD_f0DOwB8QXrQ4SqJ+BttoX6g@mail.gmail.com> <20191206124119.qe2xaffcbkcbmve3@development> <CAGjExY0Kb0-h3MqWbiYry3e40nKbYyOW3-=BO7iKLJpo8R66aw@mail.gmail.com> <20191211142310.f5qqzsgxkwt64j42@development>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox