| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Logging queries cancelled due to replication timeouts |
| Date: | 2011-10-11 18:52:29 |
| Message-ID: | 201110111852.p9BIqTr05196@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Christophe Pettus wrote:
> Greetings,
>
> Is there a combination of options that will cause a hot standby replica to log queries that are cancelled due to a replication timeout (max_standby_streaming_delay)?
Sure, how about the system view pg_stat_database_conflicts in PG 9.1?
Our docs say:
Add the <link
linkend="monitoring-stats-views-table"><structname>pg_stat_database_conflicts</></link>
system view to show queries that have been canceled and the
reason (Magnus Hagander) </para>
<para>
Cancellations can occur because of dropped tablespaces, lock
timeouts, old snapshots, pinned buffers, and deadlocks.
I assume replication cancellations are also in there, no?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | salah jubeh | 2011-10-11 19:42:12 | libpq 8.3 and 8.4 interfaces |
| Previous Message | Tom Lane | 2011-10-11 15:52:40 | Re: Should casting to integer produce same result as trunc() |