Re: Statement-level Triggers For Uniqueness Checks - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Statement-level Triggers For Uniqueness Checks
Date
Msg-id CADkLM=fskf3o2HuYYKOkyebvbqrz+BbxHH1JLq7yac1T2xOKAA@mail.gmail.com
Whole thread Raw
In response to Re: Statement-level Triggers For Uniqueness Checks  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Statement-level Triggers For Uniqueness Checks  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Fri, Jan 4, 2019 at 7:49 AM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
>
> On 25/12/2018 00:56, Corey Huinker wrote:
> > The regression diff (attached) seems to imply that the triggers simply
> > are not firing, though.
>
> The reason for this was explained by Dean.  If you take out the check
> that he mentioned, then your trigger fires but crashes.  In your changed
> unique_key_recheck(), "slot" is not initialized before use (or ever).

Thanks. I'll be revisiting this shortly. Dean's information made me
think the potential for a gain is smaller than initially imagined.


pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)
Next
From: Tom Lane
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)