From: Stephen Frost <sfrost@snowman.net>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG
Date: Wed, 1 Nov 2017 08:28:47 -0400
Message-ID: <20171101122847.GS4628@tamriel.snowman.net> (raw)
In-Reply-To: <2e3453d3-da6f-88af-05ec-7530e7f60547@catalyst.net.nz>
References: <d90474b1-6913-f3ff-d224-73fd931cdd98@cahoots.pl>
<1070071508952614@web46j.yandex.ru>
<ae7f2ee9-97ff-267e-b6dc-9399250a9314@cahoots.pl>
<20171030154706.GE4628@tamriel.snowman.net>
<7966ee9e-2241-eced-4639-e32c157b915a@catalyst.net.nz>
<20171031114756.GP4628@tamriel.snowman.net>
<2e3453d3-da6f-88af-05ec-7530e7f60547@catalyst.net.nz>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Mark,
* Mark Kirkwood (mark.kirkwood@catalyst.net.nz) wrote:
> While I agree that the scripts concerned would benefit from some
> development/qa etc, I'm really disagreeing with your point that folk
> 'should not do this'. I would like to say that folk 'should do this'
> - but try to do it well - and we should help them (isn't that idea
> kinda tied up with the whole point of these lists)?
I'm all for someone else starting up a new project to improve the
situation around backups for PG. That not going to be three shell
scripts amounting to maybe 100 lines of code and what I really am
concerned about is people seeing these simple shell scripts thinking
"oh, I'll just use these simple things" without realizing that they're
going to end up in a bad spot because those simple shell scripts aren't
sufficient to do backups with PG properly and reliably.
We could store data in a CSV file and access it through shell scripts
too and call it a database. If someone posted those as an alternative
to PG, I don't doubt that they'd get shot down pretty hard too.
These aren't just perfectionism complaints about shell scripts being
used to do backups of PG either, I've seen people using them and doing
so in ways that result in not having reliable backups which has then
lead to literally days of work be lost.
Put these shell scripts out on a github website with a big "in
development, not for production use, do not use" readme and continue to
hack on them as much as you'd like. Don't post them to these lists with
a "this is how you do backups in PG".
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
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-admin@postgresql.org
Cc: sfrost@snowman.net, mark.kirkwood@catalyst.net.nz
Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG
In-Reply-To: <20171101122847.GS4628@tamriel.snowman.net>
* 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