From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: przemyslaw@sztoch.pl
Subject: .pgdump file extension
Date: Sat, 02 Jan 2021 13:10:26 +0000
Message-ID: <160959302634.681.4635498746829191760@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/app-pgdump.html
Description:
Please consider entering a suggested name extension for pg_dump files in
custom format. For example ".pgdump". Nobody would have any doubts that this
is a database backup copy. Over the past 20 years, I have seen many times
that .dump files were treated by various administrators as some minor
temporary files. The abbreviation "PG", on the other hand, is quite
recognizable as PostgreSQL. And such less competent administrators, things
related to PostgreSQL do not touch and the backups will be safe.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, przemyslaw@sztoch.pl
Subject: Re: .pgdump file extension
In-Reply-To: <160959302634.681.4635498746829191760@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox