Re: Incremental backup

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Incremental backup
Date: 2021-10-28 21:05:13
Message-ID: e192b976-2be8-db41-0e80-4529f8e5a6f3@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/28/21 3:43 PM, Adrian Klaver wrote:
> On 10/28/21 12:23, Ron wrote:
>> On 10/28/21 2:06 PM, Adrian Klaver wrote:
>>> On 10/28/21 11:48, Ron wrote:
>>>
>>> "
>>> Logical replication is built with an architecture similar to physical
>>> streaming replication (see Section 27.2.5). It is implemented by
>>> “walsender” and “apply” processes. The walsender process starts logical
>>> decoding (described in Chapter 49) of the WAL and loads the
>>
>> Scans the (global) WAL data for only the that portion from the relevant
>> database?
>>
>> If so, definitely not the same as having per-database WAL files.
>>
>> Just as importantly, replication is not, and never will be, a substitute
>> for backups.
>
> Who says you have to use the mechanism to replicate to another database,
> why not to a file?

But WAL files store every transaction, right?  Differential and incremental
backups only send the modified pages, even if the page has been updated 1000
times.

>
> Not sure of the plausibility, still it might be interesting to find out?
>
> Also isn't a backup just an interrupted form of replication?

Highly interrupted, and usually never written back to disk in "active" form.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2021-10-28 21:09:19 Re: Incremental backup
Previous Message Michael Lewis 2021-10-28 20:56:38 Re: Model clause and