On Tue, 19 Sep 2006, Tom Lane wrote:
Marc Evans <Marc@xxxxxxxxxxxxxxxxxxx> 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.
Sorry for being terse Tom. Here is the exact commands and responses:
insert into audit_logs (audit_log_type_id,source_record,audit_format_id) values (3,20,71);
INSERT 0 1
select * from audit_logs order by timestamp desc;
id | timestamp | notify_at | audit_log_type_id | sdp_id | customer_id | customer_region_id | audit_format_id | msg_args | arg_names | source_record
-------+----------------------------+----------------------------+-------------------+--------+-------------+--------------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+---------------
15646 | 2006-09-19 17:18:10.074006 | 2006-09-19 17:18:10.190341 | 3 | | | | 71 | | |
update audit_logs set source_record = 10101 where id = 15646;
UPDATE 1
select * from audit_logs where id=15646;
id | timestamp | notify_at |
audit_log_type_id | sdp_id | customer_id | customer_region_id | audit_format_id | msg_args | arg_names | source_record
-------+----------------------------+----------------------------+-------------------+--------+-------------+--------------------+-----------------+----------+-----------+---------------
15646 | 2006-09-19 17:18:10.074006 | 2006-09-19 17:18:10.190341 | 3 | | | | 71 | | | 10101
Does that help any?
- Marc
