Re: Command to prune archive at restartpoints - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Command to prune archive at restartpoints
Date
Msg-id m2y6emu1vq.fsf@hi-media.com
Whole thread Raw
In response to Re: Command to prune archive at restartpoints  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Command to prune archive at restartpoints  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Maybe we could add a new pg_cleanuparchive binary, but we'll need some
> discussion...

Would this binary ever be used manually, not invoked by PostgreSQL? As
it depends on the %r option to be given and to be right, I don't think
so.

Therefore my take on this problem is to provide internal commands here,
that maybe wouldn't need to be explicitly passed any argument. If
they're internal they certainly can access to the information they need?

As a user, I'd find it so much better to trust PostgreSQL for proposing
sane defaults. As a developer, you will certainly find it easier to
maintain, document and distribute.

While at it, the other internal command we need is pg_archive_bypass for
the archive_command so that windows users have the /usr/bin/true option
too.

Regards,
-- 
dim


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Error with GIT Repository
Next
From: Heikki Linnakangas
Date:
Subject: Re: Command to prune archive at restartpoints