| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Bruno Almeida do Lago <teolupus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Control File |
| Date: | 2006-04-14 15:10:34 |
| Message-ID: | 9330.1145027434@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jim C. Nasby" <jnasby(at)pervasive(dot)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 ...
fi
done
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-14 15:22:23 | Re: Practical impediment to supporting multiple SSL libraries |
| Previous Message | Martijn van Oosterhout | 2006-04-14 15:00:25 | Re: Practical impediment to supporting multiple SSL libraries |