Re: locks in CREATE TRIGGER, ADD FK

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Russell Smith <mr-russ(at)pws(dot)com(dot)au>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: locks in CREATE TRIGGER, ADD FK
Date: 2005-03-23 02:54:22
Message-ID: 4240DA5E.6030005@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Huh, cluster already does that.

It does and it doesn't. Something like the first thing it does is muck
with the old table's filenode IIRC, meaning that immediately the old
table will no longer work.

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2005-03-23 02:55:53 Re: locks in CREATE TRIGGER, ADD FK
Previous Message Bruce Momjian 2005-03-23 02:51:06 Re: Prevent conflicting SET options from being set