"Jim C. Nasby" <jnasby@pervasive.com> 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.
No, just look in $PGDATA/pg_tblspc to see where the symlinks point.
I'd lean to something like
for s in $PGDATA/pg_tblspc/*do if [ x`cat $s/PG_VERSION` != x`cat $PGDATA/PG_VERSION` ] then complain ...
fidone
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.
regards, tom lane