OK I have it fixed;; just for anyone who's interested - the error was in
the base backup procedure.
When switched to plain "rsync -az" - it works like a charm.
Most probably, the fault was I assumed that you can use the rsync --update
option when doing base backup.
You cannot, especially when tim
On Tue, Feb 26, 2019 at 2:39 AM Andres Freund wrote:
>
> > 2. base backup is transferred directly to new server using
> > pg_start_backup + rsync + pg_stop_backup.
>
I excluded contents of pg_xlog only. Exact command was:
# start script
psql -Xc "select pg_start_backup('mirror to $standby', true
On Mon, Feb 25, 2019 at 11:45 PM Stephen Frost wrote:
>
> Greetings,
>
> * Filip Rembiałkowski (filip.rembialkow...@gmail.com) wrote:
> > There is a large (>5T) database on PostgreSQL 9.0.23.
>
> First off, I hope you understand that 9.0 has been *long* out of
> support and that you *really* need
Hi,
On 2019-02-25 20:06:42 +0100, Filip Rembiałkowski wrote:
> There is a large (>5T) database on PostgreSQL 9.0.23.
As Stephen said, this is long out of support.
> 2. base backup is transferred directly to new server using
> pg_start_backup + rsync + pg_stop_backup.
Do you exclude any files?
Greetings,
* Filip Rembiałkowski (filip.rembialkow...@gmail.com) wrote:
> There is a large (>5T) database on PostgreSQL 9.0.23.
First off, I hope you understand that 9.0 has been *long* out of
support and that you *really* need to upgrade to a supported version of
PostgreSQL (9.4 and up these day
Hi.
There is a large (>5T) database on PostgreSQL 9.0.23.
I would like to setup new WAL-shipping standby.
https://www.postgresql.org/docs/9.0/warm-standby.html
On my way I find unexpected issues. Here's the story, in short:
1. WAL archiving to remote archive is setup & verified
2. base backup