From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marc Evans <Marc(at)SoftwareHackery(dot)Com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Odd behavior observed |
Date: | 2006-09-19 17:15:48 |
Message-ID: | 8060.1158686148@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Marc Evans <Marc(at)SoftwareHackery(dot)Com> writes:
> On Tue, 19 Sep 2006, Tom Lane wrote:
>> What do you mean by that exactly? The example you showed seems to be
>> doing just what it's supposed to.
> In the failure mode, the source_record column always has the value NULL,
> regardless of any value specified in an insert.
What insert command is being issued exactly, and from what source? I'm
speculating about issues like stale plans or metadata caches, but you're
not providing any information about where to look.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Evans | 2006-09-19 17:21:58 | Re: Odd behavior observed |
Previous Message | Marc Evans | 2006-09-19 17:13:11 | Re: Odd behavior observed |
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Evans | 2006-09-19 17:21:58 | Re: Odd behavior observed |
Previous Message | Marc Evans | 2006-09-19 17:13:11 | Re: Odd behavior observed |