From: Ireneusz Pluta <ipluta@wp.pl>
To: pgsql-performance@postgresql.org
Subject: Physical separation of tables and indexes - where pg_xlog should go?
Date: Sat, 13 Jan 2007 10:21:21 +0100
Message-ID: <45A8A491.7050002@wp.pl> (raw)
Hello
I am going to separate physical locations of tables and their indexes, by moving indexes to a
different volume, through use of tablespaces.
As the data are going to be split, I am considering where pg_xlog should go. It is a general well
known advise to keep pg_xlog on a different physical location than data, so it would be nice to have
a third dedicated place. Unfortunately, this is not an option at the moment.
So here my question comes, what could be better:
1. keeping pg_xlog together with tables, or
2. keeping pg_xlog together with indexes?
My database is mainly readonly, with exceptinos for overnight periods, when bulk data is inserted
and updated.
Thank you
Ireneusz Pluta
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: ipluta@wp.pl
Subject: Re: Physical separation of tables and indexes - where pg_xlog should go?
In-Reply-To: <45A8A491.7050002@wp.pl>
* 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