Re: Converting WAL to SQL
| От | rajesh singarapu |
|---|---|
| Тема | Re: Converting WAL to SQL |
| Дата | |
| Msg-id | CADgiWi5LOoF7RZ4=7g-KvYJ+S9QaJ=PmiYTCJ9JCc=gdQO0b9Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Converting WAL to SQL (Fabrízio de Royes Mello <fabriziomello@gmail.com>) |
| Список | pgsql-hackers |
Thanks much for your suggestions,
I am exploring logical decoding because I have two different platforms and versions as well.So my best bet is logical decoding, but I am also wondering if somebody has done replication/migration from windows to linux or vise-a-versa at physical level with some tooling.
thanks
Rajesh
On Thu, Jan 6, 2022 at 12:21 AM Fabrízio de Royes Mello <fabriziomello@gmail.com> wrote:
On Wed, Jan 5, 2022 at 2:19 PM Julien Rouhaud <rjuju123@gmail.com> wrote:
>
> 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).
Exactly!
--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
В списке pgsql-hackers по дате отправления: