Re: pgsql: Perform less setup work for AFTER triggers at transaction start.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Perform less setup work for AFTER triggers at transaction start.
Date: 2014-10-24 04:01:33
Message-ID: 12854.1414123293@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Oct 23, 2014 at 1:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Perhaps I'm confused, but doesn't AfterTriggerEnlargeQueryState()
>> need to ensure there are at least query_depth + 1 entries in the
>> arrays? Not just query_depth?

> Hmm, I think you're right. Like this?

Yeah, that's what I meant.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2014-10-24 10:16:48 pgsql: psql: complain if pg_dump custom-format is detected
Previous Message Alvaro Herrera 2014-10-23 23:53:53 pgsql: Update README.tuplock