| From: | Dirk Mika <Dirk(dot)Mika(at)mikatiming(dot)de> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Use ctid in where clause in update from statement |
| Date: | 2019-07-01 12:13:25 |
| Message-ID: | C5E06016-DACB-4EE4-BAF6-D6F6F084867F@mikatiming.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi
Thinking about it, it _has_ to call any BEFORE trigger function
as that might change values of the row to be inserted that
could possibly change the outcome of the test.
Yeah, that was my thought, too. Unfortunately, the affected trigger changes two columns, so I can't change it to an AFTER ROW trigger.
Dirk
--
Dirk Mika
Software Developer
mika:timing GmbH
Strundepark - Kürtener Str. 11b
51465 Bergisch Gladbach
Germany
fon +49 2202 2401-1197
dirk(dot)mika(at)mikatiming(dot)de
www.mikatiming.de
AG Köln HRB 47509 * WEEE-Reg.-Nr. DE 90029884
Geschäftsführer: Harald Mika, Jörg Mika
## How2Use
## the ChampionChip by mika:timing
## https://youtu.be/qfOFXrpSKLQ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-01 14:19:39 | Re: Use ctid in where clause in update from statement |
| Previous Message | Thomas Kellerer | 2019-07-01 12:08:20 | Re: Use ctid in where clause in update from statement |