agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedRe: Clarify how triggers relate to transactions
2+ messages / 2 participants
[nested] [flat]
* Re: Clarify how triggers relate to transactions
@ 2021-05-20 15:53 Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 2+ messages in thread
From: Laurenz Albe @ 2021-05-20 15:53 UTC (permalink / raw)
To: him@nathanmlong.com; pgsql-hackers@lists.postgresql.org
On Wed, 2021-05-05 at 11:55 +0200, Laurenz Albe wrote:
> On Wed, 2021-04-28 at 13:24 +0200, Laurenz Albe wrote:
> > On Tue, 2021-04-27 at 14:26 +0000, PG Doc comments form wrote:
> > > https://www.postgresql.org/docs/current/sql-createtrigger.html mentions the
> > > word "transaction" only once, in reference specifically to constraint
> > > triggers: "They can be fired either at the end of the statement causing the
> > > triggering event, or at the end of the containing transaction; in the latter
> > > case they are said to be deferred."
> > >
> > > If I understand correctly, it would be helpful to add this sentence or a
> > > corrected version of it: "Triggers always execute in the same transaction as
> > > the triggering event, and if a trigger fails, the transaction is rolled
> > > back."
> >
> > Good idea in principle, but I'd put that information on
> > https://www.postgresql.org/docs/current/trigger-definition.html
>
> Here is a proposed patch for this.
Replying to -hackers for the commitfest app.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 2+ messages in thread
* logial replication - drop subscription.
@ 2025-05-28 20:20 PG Doc comments form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: PG Doc comments form @ 2025-05-28 20:20 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: antonio.v.botelho@gmail.com
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-droppublication.html
Description:
Hi,
I'm using a lot the logical replication.
I have to do some DDL changes, via an automatic process, on the primary.
That process drop the existing publication, which will stop the
subscription.
I kept the LSN information on the primary, perform the DDL changes on the
replica.
Than I recreate the publication, use the pg_replication_slot_advance using
the savec LSN.
When I re-enable the subscription, I have an error message in the postgres
log saying that the publication doesn't exist. However, it does have the
same name.
Can a note be added on the "DROP PUBLICATION" page to mention that dropping
a publication will compromise the logical replication process event if the
publication is recreated with the same name.
Thanks.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-05-28 20:20 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-05-20 15:53 Re: Clarify how triggers relate to transactions Laurenz Albe <laurenz.albe@cybertec.at>
2025-05-28 20:20 logial replication - drop subscription. PG Doc comments form <noreply@postgresql.org>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox