Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY
Date: 2003-06-16 08:14:29
Message-ID: 20030616081429.GC25847@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 16, 2003 at 01:17:38 -0500,
"Jim C. Nasby" <jim(at)nasby(dot)net> wrote:
>
> Yeah, so the catalog changes shouldn't be visible to anyone until after
> the ALTER is complete, right? Even if a transaction is set to read
> uncommitted, I assume it will always read only committed data from the
> catalogs...

Postgres doesn't have a read uncommitted mode for transactions.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Pflug 2003-06-16 08:27:41 Re: Groups and roles
Previous Message Jim C. Nasby 2003-06-16 06:17:38 Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY