Re: relocating the server's backup manifest code

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: relocating the server's backup manifest code
Date: 2020-04-20 18:54:41
Message-ID: CA+TgmoZGeT=wgy07oHh0y-kk90RVO4+oReY_QZp0rx9VSkj2Yg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 18, 2020 at 8:12 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> I would suggest to
> still use BackupManifest instead of Manifest in those functions and
> structures though, ...

Done in the attached, which also adds "backup_" to the type names.

After further examination, I think the Copyright header issue is
entirely separate. If someone wants to standardize that across the
source tree, cool, but this patch just duplicated the header from the
file out of which it was moving code.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
0001-Rename-exposed-identifiers-to-say-backup-manifest.patch application/octet-stream 8.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-04-20 19:37:07 Re: new heapcheck contrib module
Previous Message Peter Geoghegan 2020-04-20 18:48:50 Re: Perl modules for testing/viewing/corrupting/repairing your heap files