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

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Thorsten Schöning <tschoening(at)am-soft(dot)de>
Cc: 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 18:07:47
Message-ID: 6780C96C-3016-47C8-AD06-BF860283266C@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Jul 23, 2021, at 11:44 AM, Thorsten Schöning <tschoening(at)am-soft(dot)de> wrote:
>
> So why is that row used at all instead of simply ignored?

Because it is in the file. WAL can re-do changes, it cannot undo them.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Stephen Frost 2021-07-23 18:10:16 Re: What's the dfifference between pg_start_backup+copy+pg_stop_backup+WAL vs. pg_start_backup+pg_stop_backup+copy+WAL?
Previous Message Alvaro Aguayo 2021-07-23 18:07:08 RE: database lagging