Re: Unexpected Backend PID reported by Notification

2024-06-11 Thread Dominique Devienne
On Tue, Jun 11, 2024 at 5:29 PM David G. Johnston wrote: > On Tuesday, June 11, 2024, Dominique Devienne wrote: >> Are Stored PROCs running in a different backend? >> Are Triggers running in a different backend? > No to both. Whatever backend the SQL to invoke those was sent on is the > backend

Re: Unexpected Backend PID reported by Notification

2024-06-11 Thread David G. Johnston
On Tuesday, June 11, 2024, Dominique Devienne wrote: > > Are Stored PROCs running in a different backend? > Are Triggers running in a different backend? > No to both. Whatever backend the SQL to invoke those was sent on is the backend that executes them. David J.

Re: Unexpected Backend PID reported by Notification

2024-06-11 Thread Adrian Klaver
On 6/11/24 08:05, Dominique Devienne wrote: Hi. I have a unit test using a single connection, that simulates a client interacting with a server via a PostgreSQL "queue", i.e. a non-writable table with SECURITY DEFINER procedures to mediate writes to that table, with those PROC-initiated updates t

Unexpected Backend PID reported by Notification

2024-06-11 Thread Dominique Devienne
Hi. I have a unit test using a single connection, that simulates a client interacting with a server via a PostgreSQL "queue", i.e. a non-writable table with SECURITY DEFINER procedures to mediate writes to that table, with those PROC-initiated updates triggering pg_notify() messages (via an UPDATE