Marc Evans <[EMAIL PROTECTED]> writes:
> On Tue, 19 Sep 2006, Tom Lane wrote:
>> Hmph. You got any ON INSERT triggers or rules on that table? I can't
>> think of anything else that would interfere with data getting stored.
> No INSERT triggers. I do have a BEFORE DELETE trigger, and a pile of
> FOREIGN KEY items (which work kinda like an INSERT trigger).
Hard to see how those could be related --- but it's even harder to
credit that the INSERT would get past the parser with an explicit
reference to the new column and then not store it. I think maybe
something is applying an UPDATE to the row and losing the new value
at that point. Are any of the FKs non-default actions (ON ... SET NULL
or some such that would try to alter data instead of just erroring)?
Also, can you check the cmin field of that row and see if it's greater
than zero?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
