From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Srinivasa T N <seenutn(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Replicating an existing (huge) database |
Date: | 2022-11-28 10:24:32 |
Message-ID: | 7036a495a71b92e96c1a4f4fbd9ba0b520bf9acf.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2022-11-28 at 15:47 +0530, Srinivasa T N wrote:
> 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?
There is the "low level backup API" (pg_start_backup() and pg_stop_backup()) that
allows you to copy the data yourself, for example with storage snapshots, which
can be much faster. The essential process is like with pg_basebackup, but you
can use more efficient methods to copy the data.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Torsten Förtsch | 2022-11-28 10:28:47 | Re: Replicating an existing (huge) database |
Previous Message | Srinivasa T N | 2022-11-28 10:17:05 | Replicating an existing (huge) database |