From: piuschan <pchan@contigo.com>
To: pgsql-performance@postgresql.org
Subject: Re: stored procedure suddenly runs slowly in HOT STANDBY but fast in primary
Date: Mon, 7 Jul 2014 11:39:20 -0700 (PDT)
Message-ID: <1404758360012-5810779.post@n5.nabble.com> (raw)
In-Reply-To: <19691.1404534696@sss.pgh.pa.us>
References: <1404507888516-5810599.post@n5.nabble.com>
<19691.1404534696@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Hi Tom,
Thanks for your reply. As you said, the weirdest part is the the SP ran fine
in primary server and hot standby server. I did another test over the
weekend:
(1) restore the production DB dump to an internal server with replication
set up.
(2) ran the SP in internal hot standy DB
(3) surprisingly the SP ran fast in internal hot standby DB
So what is the possible explanations to these test results? Is there a way
to tell if the SP scans through all children event_startstop tables as you
said?
Thanks a lot,
Pius
--
View this message in context: http://postgresql.1045698.n5.nabble.com/stored-procedure-suddenly-runs-slowly-in-HOT-STANDBY-but-fas...
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pchan@contigo.com
Subject: Re: stored procedure suddenly runs slowly in HOT STANDBY but fast in primary
In-Reply-To: <1404758360012-5810779.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox