From: | Aleksander Kmetec <aleksander(dot)kmetec(at)intera(dot)si> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Inserts into sl_log tables timing out (related to the dataloss bug) |
Date: | 2009-07-22 01:42:36 |
Message-ID: | 4A666E8C.7050306@intera.si |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
there's another bug I've been seeing from time to time, but was unable to reproduce it until today.
We have statement_timeout set to 10 seconds and we would sometimes get timeouts on extremely simple statements, like
single-row inserts. I believe this is caused by a waiting TRUNCATE in logswitch_finish() blocking writes to sl_log.
To reproduce:
1. follow steps 1 to 4 as described here:
http://lists.slony.info/pipermail/slony1-general/2009-July/009663.html
2. Instead of committing in terminal 1, open a third instance of psql and run:
SET statement_timeout TO '3s';
INSERT ... -- (any table which has a logtrigger will do)
You should get the following error:
ERROR: canceling statement due to statement timeout
CONTEXT: SQL statement "INSERT INTO _clustername.sl_log_1 (log_origin, log_txid, log_tableid, log_actionseq,
log_cmdtype, log_cmddata) VALUES (1, "pg_catalog".txid_current(), $1, nextval('_clustername.sl_action_seq'), $2, $3); "
Please let me know if there's something I can do to help fix these problems.
Regards,
Aleksander
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-07-22 02:17:09 | Re: Inserts into sl_log tables timing out (related to the dataloss bug) |
Previous Message | Ow Mun Heng | 2009-07-22 01:34:47 | Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur |