Re: Converting WAL to SQL - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Converting WAL to SQL
Date
Msg-id CAOBaU_b4+gXZHgDDUdsK=wH6EW59JZRCZ7G_fJ44rYzsgrrRGQ@mail.gmail.com
Whole thread Raw
In response to Re: Converting WAL to SQL  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Converting WAL to SQL
List pgsql-hackers
On Thu, Jan 6, 2022 at 12:19 AM Bruce Momjian <bruce@momjian.us> wrote:
>
> On Tue, Jan  4, 2022 at 10:47:47AM -0300, Fabrízio de Royes Mello wrote:
> >
> >
> > What we did was decode the 9.6 wal files and apply transactions to the
> > old 9.2 to keep it in sync with the new promoted version. This was our
> > "rollback" strategy if something went wrong with the new 9.6 version.
>
> How did you deal with the issue that SQL isn't granular enough (vs.
> row-level changes) to reproduce the result reliably, as outlined here?

This is a logical decoding plugin, so it's SQL containing decoded
row-level changes.  It will behave the same as a
publication/suscription (apart from being far less performant, due to
being plain SQL of course).



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: make tuplestore helper function
Next
From: Andres Freund
Date:
Subject: Re: Throttling WAL inserts when the standby falls behind more than the configured replica_lag_in_bytes