Re: What's the dfifference between pg_start_backup+copy+pg_stop_backup+WAL vs. pg_start_backup+pg_stop_backup+copy+WAL?

From: Thorsten Schöning <tschoening(at)am-soft(dot)de>
To: <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: What's the dfifference between pg_start_backup+copy+pg_stop_backup+WAL vs. pg_start_backup+pg_stop_backup+copy+WAL?
Date: 2021-07-23 17:44:35
Message-ID: 562203777.20210723194435@am-soft.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Guten Tag Stephen Frost,
am Freitag, 23. Juli 2021 um 17:24 schrieben Sie:

> [...]Similar, once you reach the BACKUP_END record of
> a backup you know the database is consistent- but only if all of the
> files that PG was writing to were copied between the start checkpoint
> of the backup and the BACKUP_END record in the WAL.

So I am correct that the recovery process starts at what is documented
as CHECKPOINT LOCATION in the file backup_label? If the data directory
looks like a more current checkpoint might be available, that is NOT
used? Instead, all available WALs are replayed?

But how come the state of other data files into the recovery process?
that's what Laurenz Albe's example is about: A data file which is more
current than expected because that file is only copied, but the
associated changes are stored in WALs after pg_stop_backup and
therefore need to be considered lost.

Why is the data file with that additional row in B used at all? The
additional row is associated with a transaction number not available
when restoring based on CHECKPOINT LOCATION + WALs of pg_stop_backup.

So why is that row used at all instead of simply ignored? That would
actually revert the cluster to the state of pg_stop_backup, but as
said, backup outdate anyway. I still don't get why the result is not
as consistent as e.g. a crash at the same point in time instead of
doing a backup.

Mit freundlichen Grüßen

Thorsten Schöning

--
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: Thorsten(dot)Schoening(at)AM-SoFT(dot)de
Web: http://www.AM-SoFT.de/

Tel: 05151- 9468- 0
Tel: 05151- 9468-55
Fax: 05151- 9468-88
Mobil: 0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska

Für Rückfragen stehe ich Ihnen sehr gerne zur Verfügung.

Mit freundlichen Grüßen

Thorsten Schöning

Tel: 05151 9468 0
Fax: 05151 9468 88
Mobil:
Webseite: https://www.am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH i.G. ist ein Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

AM-Soft IT-Service - Bitstore Hameln GmbH i.G.
Brandenburger Str. 7c
31789 Hameln
Tel: 05151 9468 0

Bitstore IT-Consulting GmbH
Zentrale - Berlin Lichtenberg
Frankfurter Allee 285
10317 Berlin
Tel: 030 453 087 80

CBS IT-Service - Bitstore Kaulsdorf UG
Tel: 030 453 087 880 1

Büro Dallgow-Döberitz
Tel: 03322 507 020

Büro Kloster Lehnin
Tel: 033207 566 530

PCE IT-Service - Bitstore Darmstadt UG
Darmstadt
Tel: 06151 392 973 0

Büro Neuruppin
Tel: 033932 606 090

ACI EDV Systemhaus - Bitstore Dresden GmbH
Dresden
Tel: 0351 254 410

Das Systemhaus - Bitstore Magdeburg GmbH
Magdeburg
Tel: 0391 636 651 0

Allerdata.IT - Bitstore Wittenberg GmbH
Wittenberg
Tel: 03491 876 735 7

Büro Liebenwalde
Tel: 033054 810 00

HSA - das Büro - Bitstore Altenburg UG
Altenburg
Tel: 0344 784 390 97

Bitstore IT - Consulting GmbH
NL Piesteritz
Piesteritz
Tel: 03491 644 868 6

Solltec IT-Services - Bitstore Braunschweig UG
Braunschweig
Tel: 0531 206 068 0

MF Computer Service - Bitstore Gütersloh GmbH
Gütersloh
Tel: 05245 920 809 3

Firmensitz: AM-Soft IT-Service - Bitstore Hameln GmbH i.G. , Brandenburger Str. 7c , 31789 Hameln
Geschäftsführer Janine Galonska

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Pepe TD Vo 2021-07-23 17:52:21 database lagging
Previous Message Bruce Momjian 2021-07-23 17:22:31 Re: Call to package procedure in Oracle not working