Bug#705219: pg_checksystem does not respect start.conf

[Christoph Berg]

Re: Stephen Frost 2013-04-11 20130411130202.ge4...@tamriel.snowman.net
 In our environment, we have shared storage which allows us to fail over
 between two systems, however, we intentionally keep on the filesystems
 mounted for those clusters which are running on the current system, to
 reduce the chances of two postmasters (on different systems) trying to
 access/use the same database files.

Fwiw, what we are doing for a customer is to put the config in some
directory on the data partition, and point a symlink there from
/etc/postgresql/$version. That way, the config is also invisible while
the filesystem is on the other node and hence I've never seen this
problem.

 My suggestion would be for pg_checksystem to skip checking clusters
 which are marked as 'disabled' in start.conf.  Another option might be
 for it to more cleanly handle the error case from 'df'.

PgCommon.pm is now ignoring all errors from df. As pg_checksystem is
just meant as a sanity check, that sounded like the best option for
me.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#705219: pg_checksystem does not respect start.conf

[Stephen Frost]

Package: postgresql-common
Version: 141

postgresql-common provides a way to mark clusters as auto, manual,
or disabled.  When a cluster is marked as disabled, however,
pg_checksystem will still try to verify that the cluster is valid and
will attempt to do things like check the filesystem associated with the
cluster.

In our environment, we have shared storage which allows us to fail over
between two systems, however, we intentionally keep on the filesystems
mounted for those clusters which are running on the current system, to
reduce the chances of two postmasters (on different systems) trying to
access/use the same database files.  pg_checksystem throws an error in
this case though because the 'df' doesn't work against the cluster which
we have marked as 'disabled'.

My suggestion would be for pg_checksystem to skip checking clusters
which are marked as 'disabled' in start.conf.  Another option might be
for it to more cleanly handle the error case from 'df'.

Thanks,

Stephen


signature.asc
Description: Digital signature