From: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: unknown error message |
Date: | 2006-07-24 17:49:03 |
Message-ID: | ea313l$kd6$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Tom,
in the mean time I've traced the problem down to a 'CONSTRAINT' declared
as 'DEFERRABLE INITIALLY DEFERED'. As soon as I remove that constraint
the transaction commits nicely. BTW: I'm running in ISOLATION LEVEL
SERIALIZABLE, if that matters.
Has something changed so that it's worth trying current CVS? I'll try to
come up with a test case, the problem is not easy to isolate, though.
Regards
Markus
Tom Lane wrote:
> Markus Schiltknecht <markus(at)bluegap(dot)ch> writes:
>> I'm getting the following error from my python script, which tries to
>> insert lots of data in one transaction:
>> libpq.OperationalError: ERROR: failed to fetch new tuple for AFTER trigger
>
> That's not supposed to happen. Can you provide a test case?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-24 18:54:26 | Re: unknown error message |
Previous Message | John DeSoi | 2006-07-24 17:28:30 | Re: Why can't I connect to postgres? |