Tom Lane wrote:
>> Foreign-key constraints:
>> "dashboard_tuginstance_node_id_fkey" FOREIGN KEY (node_id)
>> REFERENCES nodes(id) DEFERRABLE INITIALLY DEFERRED
> This is what's creating the limitation.
So, I'm working around it by creating the new columns with the default
value that I want populated, and then resetting the default. This works,
but it doesn't feel like a best practice.
Can someone recommend a better way to say, consolidate 3 columns down to
2 and conditionally move contents around to the new columns, inside of a
transaction involving ALTER TABLE calls?
I'm just wondering if there is a better solution than what I've done.
Michael P. Soulier <michael_soulier(at)mitel(dot)com>, 613-592-2122 x2522
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein
In response to
pgsql-general by date
|Next:||From: Alan Hodgson||Date: 2009-04-30 22:19:25|
|Subject: Re: pg_dump and pg_restore problem|
|Previous:||From: Merlin Moncure||Date: 2009-04-30 19:30:33|
|Subject: Re: How to begin to debug FATAL: invalid frontend message type 77 error messages?|