Re: [PATCH] Space reservation v02 - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [PATCH] Space reservation v02
Date
Msg-id 87bpton358.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: [PATCH] Space reservation v02  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: [PATCH] Space reservation v02  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCH] Space reservation v02  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:

> Zdenek Kotala wrote:
>> Bruce Momjian píše v pá 30. 01. 2009 v 10:41 -0500:
>>> Well, I was thinking the new pg_class column would allow the upgrade to
>>> verify the pre-upgrade script was run properly, but a flat file works
>>> just as well if we assume we are going to pre-upgrade in one pass.
>>
>> Flat file or special table for pg_upgrade will work fine.
>
> Right, there's no difference in what you can achieve, whether you store the
> additional info in a flat file, special table or extra pg_class columns. If you
> can store something in pg_class, you can store it elsewhere just as well.

Well having a column in pg_class does have some advantages. Like, you could
look at the value from an sql session more easily. And if there are operations
which we know are unsafe -- such as adding columns -- we could clear it from
the server side easily.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production
Tuning


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: mingw check hung
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCH] Space reservation v02