pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: sparikh <sparikh@ecotality.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hot Standby performance issue
Date: Mon, 21 Oct 2013 17:00:45 -0700 (PDT)
Message-ID: <1382400045239-5775361.post@n5.nabble.com> (raw)
In-Reply-To: <5265B562.3040407@fuzzy.cz>
References: <1381869626548-5774673.post@n5.nabble.com>
	<1382291901534-5775181.post@n5.nabble.com>
	<526460B7.3020008@fuzzy.cz>
	<1382367933794-5775257.post@n5.nabble.com>
	<52658780.1040002@fuzzy.cz>
	<1382390332002-5775332.post@n5.nabble.com>
	<5265A28E.4060601@fuzzy.cz>
	<1382396377294-5775349.post@n5.nabble.com>
	<5265B562.3040407@fuzzy.cz>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

> Do you suggest if I remove all the data files from /data/base folder 
> of standby and again rebuild using rsync from primary ? do you see 
> any issues there.? This is just to rule out any fragmentation on 
> standby side. 

The EXPLAIN really should not do much I/O. I doubt it has anything to do 
with fragmentation, so I doubt this is going to help. 

Actually I was referring to this in the context of addressing main
underlying performance issue, not EXPLAIN. Sorry, I may not have
communicated it correctly.

Even strance does not seem to be installed.

The filesytem type it shows to me ext3.

Thanks.



--
View this message in context: http://postgresql.1045698.n5.nabble.com/Hot-Standby-performance-issue-tp5774673p5775361.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



view thread (31+ messages)  latest in thread

Message-ID: <1382400045239-5775361.post@n5.nabble.com>
Permalink:  ../1382400045239-5775361.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1382400045239-5775361.post@n5.nabble.com

 · 

reply
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: sparikh@ecotality.com
  Subject: Re: Hot Standby performance issue
  In-Reply-To: <1382400045239-5775361.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