Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Perform less setup work for AFTER triggers at transaction start. - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Perform less setup work for AFTER triggers at transaction start.
Date
Msg-id CA+TgmoYX6PRy33uesTn0K8v8CHcUuWtOF8G_qt6gwaWXpKu65g@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Perform less setup work for AFTER triggers at transaction start.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Perform less setup work for AFTER triggers at transaction start.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tree view 
On Thu, Oct 23, 2014 at 1:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <rhaas@postgresql.org> writes:
>> Perform less setup work for AFTER triggers at transaction start.
>
> 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?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: In type_sanity, check I/O functions of built-in types are not vo
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Update README.tuplock