Re: Replicating an existing (huge) database

From: Torsten Förtsch <tfoertsch123(at)gmail(dot)com>
To: Srinivasa T N <seenutn(at)gmail(dot)com>
Cc: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Replicating an existing (huge) database
Date: 2022-11-28 10:28:47
Message-ID: CAKkG4_=UrqbYZ6XGAu6Yc=CwmFnrDW2=io350PpEj9xLJvR6Og@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

You can set up wal archiving and set restore_command before you start the
replica. Then you can use pg_basebackup with `-Xnone --no-slot`.
Alternatively or in combination, use a quicker backup as Laurenz explained.

On Mon, Nov 28, 2022 at 11:17 AM Srinivasa T N <seenutn(at)gmail(dot)com> wrote:

> Hi All,
> I am using postgresql 12. As part of streaming replication setup, I
> run pg_basebackup on the slave which copies the database from master to
> slave. But the database is huge and it takes around 2 to 3 days for the
> pg_basebackup to finish. When pg_basebackup is running, a huge number of
> wal files are generated on the master which occupies a lot of space (even
> though it is for 2-3 days, disk space is low). Is there any other way to
> start replication without using pg_baseback?
>
> Regards,
> Seenu.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message yin.zhb@163.com 2022-11-28 12:37:37 how to implement add using upsert and trigger?
Previous Message Laurenz Albe 2022-11-28 10:24:32 Re: Replicating an existing (huge) database