pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shaun Thomas <sthomas@optionshouse.com>
To: Niels Kristian Schjødt <nielskristian@autouncle.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Optimize update query
Date: Wed, 28 Nov 2012 12:01:41 -0600
Message-ID: <50B65185.6010005@optionshouse.com> (raw)
In-Reply-To: <1E87B44E-A22E-4790-A737-C8EAF504C58E@autouncle.com>
References: <1C199C0D-13DF-47B3-944A-B0560C6D2E5A@autouncle.com>
	<50B61ABF.4070000@optionshouse.com>
	<50B6223B.6000100@mejor.pl>
	<DUB104-W48E83E17609D570C42B5AD8F5D0@phx.gbl>
	<CAC9DA03-64C2-45E2-9B88-703F9768F574@autouncle.com>
	<50B641AD.3020204@optionshouse.com>
	<1E87B44E-A22E-4790-A737-C8EAF504C58E@autouncle.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

On 11/28/2012 11:44 AM, Niels Kristian Schjødt wrote:

> Thanks a lot - on the server I already have one additional SSD 250gb
> disk, that I don't use for anything at the moment.

Goooood. An SSD would actually be better for your data, as it follows
more random access patterns, and xlogs are more sequential. But it's
better than nothing.

And yes, you'd be better off with a RAID-1 of two of these SSDs, because
the xlogs are critical to database health. You have your archived copy
due to the rsync, which helps. But if you had a crash, there could
potentially be a need to replay unarchived transaction logs, and you'd
end up with some data loss.

> BTW. as you might have seen from the .conf I have a second slave
> server with the exact same setup, which currently runs as a hot
> streaming replication slave. I might ask a stupid question here, but
> this does not affect the performance of the master does it?

Only if you're using synchronous replication. From what I saw in the
config, that isn't the case.


--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


-- 
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 (34+ messages)  latest in thread

Message-ID: <50B65185.6010005@optionshouse.com>
Permalink:  ../50B65185.6010005@optionshouse.com/
Also on:    postgresql.org/message-id/50B65185.6010005@optionshouse.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: sthomas@optionshouse.com, nielskristian@autouncle.com
  Subject: Re: Optimize update query
  In-Reply-To: <50B65185.6010005@optionshouse.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