On Fri, Apr 14, 2006 at 11:10:34AM -0400, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > As for adding checks to startup scripts, that's a PITA because > > those scripts will have no idea of where tablespaces might be defined, > > so you'd have to hard-code that info in. <snip> > OTOH you could argue that it'd be just as reasonable for the postmaster > to make this check, seeing that it does go to the trouble of verifying > the contents of $PGDATA/PG_VERSION.
Yup. Plus it seems rather silly to expect every port/package of PostgreSQL to add code to check for functional tablespace mounts. Perhaps an easy means would be to put a PG_VERSION file in each tablespace when it's created and then check all of them. Tablespaces arguably make it slightly easier to accidentally try and mount something from a different version... -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
