Re: Doc: Move standalone backup section, mention -X argument

From: Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Doc: Move standalone backup section, mention -X argument
Date: 2025-04-15 14:48:20
Message-ID: c7871c9d-c6bd-462f-b8c7-2c4a0ca753f3@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/16/25 2:19 PM, vignesh C wrote:
> I noticed that Alvaro's comment from [1] is not yet addressed, I have
> changed the status of commitfest entry to Waiting on Author, please
> address them and change the status back to Needs review.
> [1] - https://www.postgresql.org/message-id/202502101154.bmb536npfl5e%40alvherre.pgsql
>
> Regards,
> Vignesh

Hi,

You will find a patch for the proposed changes attached to this mail.

The menu is now:

25.1. SQL Dump
25.1.1. Restoring the Dump
25.1.2. Using pg_dumpall
25.1.3. Handling Large Databases
25.2. Physical Backups Using Continuous Archiving
25.2.1. Built-In Standalone Backups
25.2.2. Setting Up WAL Archiving
25.2.3. Making a Base Backup
25.2.4. Making an Incremental Backup
25.2.5. Making a Base Backup Using the Low Level API
25.2.6. Recovering Using a Continuous Archive Backup
25.2.7. Timelines
25.2.8. Tips and Examples
25.2.9. Caveats
25.3. File System Level Backup

I slightly modified section 25.2.1 and 25.3 as proposed.

--
Benoit Lobréau
Consultant
http://dalibo.com

Attachment Content-Type Size
v2-0001-Reorganize-the-backup-section.patch text/x-patch 14.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-04-15 14:52:09 Re: FmgrInfo allocation patterns (and PL handling as staged programming)
Previous Message Tom Lane 2025-04-15 14:37:36 Re: use correct variable in error message in _allocAH function (pg_backup_archiver.c)