| 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-13 10:51:55 |
| Message-ID: | CAGjExY2xQa8hxEYBTDDv6Y66V2=D0HEDsmLt42ZVupC3BxsLsQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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(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
>
| Attachment | Content-Type | Size |
|---|---|---|
| pg_memory_context.txt | text/plain | 16.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-12-13 13:20:36 | Re: Memory leak (possibly connected to postgis) leading to server crash |
| Previous Message | Manuel Rigger | 2019-12-13 09:56:09 | Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c", Line: 89) |