Re: Control File
| От | Bruno Almeida do Lago |
|---|---|
| Тема | Re: Control File |
| Дата | |
| Msg-id | 444389cc.0e15bcb5.40fd.51cf@mx.gmail.com обсуждение исходный текст |
| Ответ на | Re: Control File (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Control File
|
| Список | pgsql-hackers |
Tom,
With the new tablespace scenario in mind, how do you see this check feature
being implemented: as a script or inside the code?
As I said before, I apply for the creation of this patch. We just need to
decide the best way to implement it.
Regards,
Bruno Almeida do Lago
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Saturday, April 15, 2006 4:11 PM
To: Jim C. Nasby
Cc: Bruce Momjian; Bruno Almeida do Lago; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Control File
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> 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...
I believe we already do put a PG_VERSION file in each tablespace, but
AFAIR there is no subsequent check on their contents.
regards, tom lane
В списке pgsql-hackers по дате отправления: