Re: Stephen Frost 2013-04-11 <[email protected]> > 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 -- [email protected] | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
