Re: OOM on EXPLAIN with lots of nodes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexey Bashtanov <bashtanov(at)imap(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OOM on EXPLAIN with lots of nodes
Date: 2015-01-15 18:45:51
Message-ID: 16015.1421347551@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jan 13, 2015 at 8:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Not sure whether to just commit this to HEAD and call it a day, or to
>> risk back-patching.

> I think we need to back-patch something; that's a pretty nasty
> regression, and I have some EDB-internal reports that might be from
> the same cause.

OK. I went ahead and made the necessary code changes to avoid changing
the struct size in released branches, as per Heikki's idea.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-01-15 18:47:05 Re: hung backends stuck in spinlock heavy endless loop
Previous Message Heikki Linnakangas 2015-01-15 18:36:00 Re: compress method for spgist - 2