From: Bruce Momjian <bruce@momjian.us>
To: przemyslaw@sztoch.pl
To: pgsql-docs@lists.postgresql.org
Subject: Re: .pgdump file extension
Date: Tue, 5 Jan 2021 12:38:56 -0500
Message-ID: <20210105173856.GJ7432@momjian.us> (raw)
In-Reply-To: <160959302634.681.4635498746829191760@wrigleys.postgresql.org>
References: <160959302634.681.4635498746829191760@wrigleys.postgresql.org>
On Sat, Jan 2, 2021 at 01:10:26PM +0000, PG Doc comments form wrote:
> 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.
This is an interesting idea, but perhaps pgdb.dump might be better. I
agree db.dump isn't clear that it is related to Postgres.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
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: bruce@momjian.us, przemyslaw@sztoch.pl, pgsql-docs@lists.postgresql.org
Subject: Re: .pgdump file extension
In-Reply-To: <20210105173856.GJ7432@momjian.us>
* 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