| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsqlrpms-hackers(at)pgfoundry(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Safer auto-initdb for RPM init script |
| Date: | 2006-08-25 14:49:57 |
| Message-ID: | 873bbkvpii.fsf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Comments? Anyone see a better way?
Well the truly bullet-proof mechanism would be to check every data file on
every open. You could have a header with some kind of unique tag generated at
initdb time and the backend could ensure it matches the same tag in the
control flag whenever you open a data file.
That might be too expensive though I don't see data files getting opened all
that frequently. You could do the same thing for free by putting the tag in
the file names though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-25 14:54:57 | Re: Safer auto-initdb for RPM init script |
| Previous Message | Tom Lane | 2006-08-25 14:45:35 | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init script |