Postgres Pro
Downloads
Home   >   mailing lists

Re: [GENERAL] Bad planning data resulting in OOM killing of postgres - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] Bad planning data resulting in OOM killing of postgres
Date
Msg-id 28429.1487108330@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Bad planning data resulting in OOM killing of postgres  (David Hinkle <hinkle@cipafilter.com>)
Responses Re: [GENERAL] Bad planning data resulting in OOM killing of postgres  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view 
David Hinkle <hinkle@cipafilter.com> writes:
> Thanks guys, here's the information you requested:
> psql:postgres@cipafilter = show work_mem;
>  work_mem
> ──────────
>  10MB
> (1 row)

[ squint... ]  It should absolutely not have tried to hash a 500M-row
table if it thought work_mem was only 10MB.  I wonder if there's an
integer-overflow problem or something like that.

            regards, tom lane

pgsql-general by date:

Previous
From: Nikolai Zhubr
Date:
Subject: Re: [GENERAL] Re: Causeless CPU load waves in backend, on windows,9.5.5 (EDB binary).
Next
From: Patrick B
Date:
Subject: [GENERAL] get inserted id from transaction - PG 9.2