Re: locking of referenced table during constraint

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Shattuck <ss(at)technicalpursuit(dot)com>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: locking of referenced table during constraint
Date: 2002-09-05 04:49:56
Message-ID: 26131.1031201396@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Scott Shattuck <ss(at)technicalpursuit(dot)com> writes:
> ... I don't understand why an exclusive table-level lock is being
> taken out to add a trigger.

Well, that's a schema change; it makes sense to me to forbid access
while we're changing a table's schema.

I think this discussion may just be a miscommunication: it's not clear
to me whether you're complaining about adding a trigger or just firing
a trigger. The former is not a time-critical task in my book ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-09-05 04:58:06 TODO item on triggers
Previous Message Scott Shattuck 2002-09-05 04:29:24 Re: locking of referenced table during constraint