Logging queries cancelled due to replication timeouts

Started by Christophe Pettusover 14 years ago2 messagesgeneral
Jump to latest
#1Christophe Pettus
xof@thebuild.com

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)?

--
-- Christophe Pettus
xof@thebuild.com

#2Bruce Momjian
bruce@momjian.us
In reply to: Christophe Pettus (#1)
Re: Logging queries cancelled due to replication timeouts

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@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +