From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Christian Mock <cm(at)coretec(dot)at> |
Cc: | <pgsql-general(at)postgresql(dot)org>, Andrew Sullivan <andrew(at)libertyrms(dot)info> |
Subject: | Re: stupid Q regarding "UPDATE waiting" |
Date: | 2002-08-28 15:20:30 |
Message-ID: | 20020828081705.O85460-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 28 Aug 2002, Christian Mock wrote:
> On Tue, Aug 27, 2002 at 02:08:17PM -0400, Andrew Sullivan wrote:
>
> > > hangs until the first transaction is done; the related postgres process
> > > shows as "UPDATE waiting" in ps.
> >
> > Do you have referential integrity on any of these? That's the usual
> > suspect in these cases.
>
> I see. One of the tables that are inserted into in the long-running
> transaction references the table that gets updated in the "UPDATE waiting"
> transaction. But the referencing column is always NULL on import.
>
> Does that mean that there's a table-level lock? Can I get around this?
Hmm, I may have missed it, but can you give an example of the actual
statments and schema?
The only workarounds I know about are hacking the trigger functions and
making the constraints deferred (which is only a partial solution, but
often helps in practice).
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2002-08-28 15:23:23 | Re: Performance Tuning / RAM Usage |
Previous Message | Bruce Momjian | 2002-08-28 15:17:28 | Re: psql 7.2.1 on S/390 |