Date: Mon, 7 Jul 2014 11:39:20 -0700 (PDT)
From: piuschan <pchan@contigo.com>
To: pgsql-performance@postgresql.org
Message-ID: <1404758360012-5810779.post@n5.nabble.com>
In-Reply-To: <19691.1404534696@sss.pgh.pa.us>
References: <1404507888516-5810599.post@n5.nabble.com>
 <19691.1404534696@sss.pgh.pa.us>
Subject: Re: stored procedure suddenly runs slowly in HOT STANDBY but fast
 in primary
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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-fast-in-primary-tp5810599p5810779.html
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