From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: WAL replication from an Old Production server
Date: Tue, 13 Dec 2022 09:57:04 -0600
Message-ID: <accd61e0-9a55-73ee-6554-b2741f539111@gmail.com> (raw)
In-Reply-To: <CAKgGyB9F9DcwuLrkVorXLx8MLU8XxBbT2ziKDr2YssAmeivDOw@mail.gmail.com>
References: <CAKgGyB9F9DcwuLrkVorXLx8MLU8XxBbT2ziKDr2YssAmeivDOw@mail.gmail.com>
On 12/13/22 04:16, KK CHN wrote:
> List,
>
> I have to perform WAL Streaming replication configuration for
>
> An existing small production server with 600 GB of size grown over for
> two years. There is no WAL replication in place configured as of now.
>
> 2. If I want to perform WAL replication to a new Standby Server
> How to copy the 600 GB of DB data to Standby? OR when we configure
> the WAL replication attributes on primary and standby will the Standby
> automatically copy all the 600 GB data to the defined WAL archive dir ?
>
> Or Do I need to manually copy the data directory of primary by SCP over
> NW or by copying the data directory of Primary to a USB disk and
> manually copy to the WAL archive_dir folder defined in the standby ?
> What method to follow ? why?
>
> 3. In WAL streaming replication what ports/protocols are used for copying
> the data directory of primary to archive_dir of standby server and for
> Streaming ?
The Google search "how to set up streaming replication in postgresql 12"
answered all my questions.
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: WAL replication from an Old Production server
In-Reply-To: <accd61e0-9a55-73ee-6554-b2741f539111@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox