Re: Deferred constraint trigger semantics

2022-05-10 Thread Laurenz Albe
On Tue, 2022-05-10 at 17:46 -0700, Bryn Llewellyn wrote: > I looked at the sections "CREATE TRIGGER" and "Chapter 39. Triggers" in the > Current PG doc. > But I failed to find any information about the semantics of the deferred > constraint trigger > or about the use cases that motivated this fea

Re: Deferred constraint trigger semantics

2022-05-10 Thread David G. Johnston
On Tue, May 10, 2022 at 7:52 PM Bryn Llewellyn wrote: > > *david.g.johns...@gmail.com wrote:* > > * However, SQL commands executed in a row-level BEFORE trigger will see > the effects of data changes for rows previously processed in the same outer > command. This requires caution, since the orde

Re: Deferred constraint trigger semantics

2022-05-10 Thread Bryn Llewellyn
> david.g.johns...@gmail.com wrote: > >> b...@yugabyte.com wrote: >> >> INFO: trg fired. new.v = 80, n = 8 >> >> It shows the expected "new" value each time it fires. And yet the query >> reflects the table content on statement completion. This seems to be very >> strange. > > From the docum

Re: Deferred constraint trigger semantics

2022-05-10 Thread David G. Johnston
On Tue, May 10, 2022 at 5:47 PM Bryn Llewellyn wrote: > > INFO: trg fired. new.v = 80, n = 8 > > It shows the expected "new" value each time it fires. And yet the query > reflects the table content on statement completion. This seems to be very > strange. > >From the documentation: "Row-level

Deferred constraint trigger semantics

2022-05-10 Thread Bryn Llewellyn
SUMMARY === I looked at the sections "CREATE TRIGGER" and "Chapter 39. Triggers" in the Current PG doc. But I failed to find any information about the semantics of the deferred constraint trigger or about the use cases that motivated this feature. Nor could I find any code examples. Interne

Re: PLPGSQL - extra column existence in trigger

2022-05-10 Thread Peter J. Holzer
On 2022-05-07 15:02:09 +0200, Durumdara wrote: > We stored the username in a temporary table which was created by the client > app. > With this technique we can log these names in triggers too. > > Now we extend it with user id and later the comp name. > > Because we can update the client applica

Re: Fedora 36

2022-05-10 Thread Adrian Klaver
On 5/10/22 09:38, Kieran McCusker wrote: Hi Is there any timeline for a Fedora 36 repository as it should be released today? Looks like it is there: https://yum.postgresql.org/packages/#pg14 Many thanks Kieran -- Adrian Klaver adrian.kla...@aklaver.com

Fedora 36

2022-05-10 Thread Kieran McCusker
Hi Is there any timeline for a Fedora 36 repository as it should be released today? Many thanks Kieran