Re: Control File

From: "Bruno Almeida do Lago" <teolupus(at)gmail(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Jim C(dot) Nasby'" <jnasby(at)pervasive(dot)com>
Cc: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Control File
Date: 2006-04-17 12:28:01
Message-ID: 444389cc.0e15bcb5.40fd.51cf@mx.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Saturday, April 15, 2006 4:11 PM
To: Jim C. Nasby
Cc: Bruce Momjian; Bruno Almeida do Lago; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Control File

"Jim C. Nasby" <jnasby(at)pervasive(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2006-04-17 12:33:57 plpython improvements on patches
Previous Message Bruno Almeida do Lago 2006-04-17 12:15:45 Re: Control File