From: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com> |
---|---|
To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | 9.0 standby - could not open file global/XXXXX |
Date: | 2019-02-25 19:06:42 |
Message-ID: | CAP_rwwmG2aOjCEWdag5fEAYM=LX9_9LxJRYHc9MiStWZaqOz0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 is transferred directly to new server using
pg_start_backup + rsync + pg_stop_backup.
3. recovery.conf is created
4. Server is started and consumes all the remaining WAL segments
accumulated in the archive - finishing with optimistic message LOG:
consistent recovery state reached at 9FC1/112BEE10.
5. When I go to postgres on the standby and try to connect system
"postgres" database psql: FATAL: could not open file "global/11819":
No such file or directory
I guessed the OID refereds to the pg_authid, but other system tables
might be affected too.
What could be wrong here?
Thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Tanzer | 2019-02-25 19:19:09 | Re: Recommended way to enable data-checksums on Centos 7? |
Previous Message | wambacher | 2019-02-25 18:42:55 | update table with suppress_redundant_updates_trigger() |