| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sri Linux <srilinux09(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Need help with PITR for PostgreSQL 9.4.5 |
| Date: | 2020-06-25 04:36:24 |
| Message-ID: | CAKFQuwabUucmjzB2uyoq31qM4pcgP_rOGMQ4jA5P+itCDE9Xxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
The version you are running is neither up-to-date for its major version
(9.4) nor is the major version being supported.
https://www.postgresql.org/support/versioning/
Thoug a functioning backup is good to have before upgrading, especially
major versions.
On Wednesday, June 24, 2020, Sri Linux <srilinux09(at)gmail(dot)com> wrote:
>
> I am trying to do PINT backup and recovery for the standalone
> database which is not in a cluster.
>
That is not possible. Its unclear what exactly you mead/did though.
Consider sharing actual commands/scripts.
< 2020-06-22 16:34:08.487 CDT >LOG: WAL file is from different database
> system: WAL file database system identifier is 6840038030519879233,
> pg_control database system identifier is 6841285371464745049.
>
You cannot PITR if the WAL doesn’t match the base backup for the cluster
you are trying to restore.
https://www.postgresql.org/docs/9.4/continuous-archiving.html
Or, probably better, consider using a third-party system.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajnish Vishwakarma | 2020-06-25 04:49:49 | Error in Table Creation |
| Previous Message | Sri Linux | 2020-06-25 04:00:05 | Need help with PITR for PostgreSQL 9.4.5 |