Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tom Dunstan" <pgsql(at)tomd(dot)cc>
Cc: "Brendan Jurd" <direvus(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Bruce Momjian" <momjian(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing
Date: 2008-04-25 22:28:57
Message-ID: 2143.1209162537@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
"Tom Dunstan" <pgsql(at)tomd(dot)cc> writes:
> On Sat, Apr 26, 2008 at 2:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Further, as already noted, if you do have to rewrite then a series of
>> manual ALTER COLUMN TYPE operations would probably be a *better* answer
>> than a monolithic implementation, because of the locking problems
>> involved in doing it in one transaction.

> I don't understand this if it's calling option 2 the monolithic
> implementation.

No, I was imagining an option-1 implementation trying to support
rewriting of all affected tables in a single "monolithic" command.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Jacques CaronDate: 2008-04-25 23:27:45
Subject: FSM fill ratio
Previous:From: Tom DunstanDate: 2008-04-25 22:01:37
Subject: Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing

pgsql-committers by date

Next:From: User EggyknapDate: 2008-04-25 23:15:32
Subject: pllolcode - pllolcode: Remove debug code
Previous:From: Tom DunstanDate: 2008-04-25 22:01:37
Subject: Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group