From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: log shipping with pg_receivewal |
Date: | 2021-12-14 05:40:12 |
Message-ID: | CAFiTN-sfLT2XW45G4Ufwq-QzPxxE-eOx48MvS8eu6pUwgq0QdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 14, 2021 at 9:55 AM Marc Millas <marc(dot)millas(at)mokadb(dot)com> wrote:
>
> Hi,
> postgres 13 question,
>
> if I setup pg_receivewal from a primary instance to a given directory, and then setup a standby with a restore_command pointing to that directory,, the changes on the primary are applied on the standby at each wal change. And this, even if I run pg_receivewal with the --synchronous option.
>
> My question: as the synchronous option is supposed to make pg_receivewal write transaction immediately in the wal files, is there a way to ask the standby to apply them on the fly ie. without waiting a wal file change ?
I don't think that can be done, actually, the wal_receiver process is
running in the same cluster so we can interact with that process and
know exactly up to what LSN it has flush and what wal data is valid to
be applied and wal receiver also continues to append more WAL to the
same file. But pg_receivewal is a separate utility so this can serve
as an archive location that means we can restore the complete WAL file
only.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-12-14 06:29:34 | Re: locks within select |
Previous Message | Michael Paquier | 2021-12-14 05:38:55 | Re: log shipping with pg_receivewal |