| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, phb07(at)apra(dot)asso(dot)fr, Andrew Gierth <rhodiumtoad(at)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: BUG #14808: V10-beta4, backend abort |
| Date: | 2017-09-14 21:10:25 |
| Message-ID: | CAEepm=2st+4LzooeaALSWJUAX_xe8Vve9VDr1BQkdJFiOhS-Kw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Sep 15, 2017 at 8:43 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> Note that
> TransitionCaptureState already holds tuplestores for each operation
> (INSERT, UPDATE, DELETE)
Erm, that's not quite true -- it only separates INSERT and UPDATE for
now. It would need to be true, so it would need to gain one more to
have the full set.
> ... perhaps using a flag in the TransitionCaptureState to prevent multiple
> firings.
Of course that would need to be per-trigger, not just one flag per
TCS. Also the change in firing rules for multiply-referenced tables
would apply also when there are no TTs involved, so perhaps TCS is not
a good place for that state.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-09-14 21:15:53 | Re: BUG #14813: pg_get_serial_sequence does not return seqence name for IDENTITY columns |
| Previous Message | Thomas Munro | 2017-09-14 20:43:25 | Re: BUG #14808: V10-beta4, backend abort |