pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Koczan <pjkoczan@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: best practices for separating data and logs
Date: Wed, 02 Jan 2008 13:10:01 -0500
Message-ID: <17603.1199297401@sss.pgh.pa.us> (raw)
In-Reply-To: <4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.com>
References: <4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.com>

"Peter Koczan" <pjkoczan@gmail.com> writes:
> I'm planning a lot of changes for migrating to PostgreSQL 8.3, among
> them being a better way of separating data and logs (transaction logs,
> that is).

> Currently, the OS and log data are on one disk system, and the data
> (including configs) are on the other disk system. After creating the
> database cluster, I copy the pg_xlog directory to the OS system and
> symlink it from the database.

> So, I'm wondering...

> - Are there any best practices, or better practices, than symlinking?

I believe 8.3's initdb has an explicit option for making pg_xlog be a
symlink to someplace.  The results aren't different from doing it
manually, but it saves a step (and a chance for mistake).

> - How do other people have this set up, or recommend setting this up
> (e.g. also moving pg_clog or other things as well)?

I think consensus is that pg_clog is best treated as part of the data.
The point of moving xlog is that the heads on that drive will never have
to move away from the current xlog tip; as soon as you put something
else on that drive, you ruin the performance benefit.

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <17603.1199297401@sss.pgh.pa.us>
Permalink:  ../17603.1199297401@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17603.1199297401@sss.pgh.pa.us

 · 

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pjkoczan@gmail.com
  Subject: Re: best practices for separating data and logs
  In-Reply-To: <17603.1199297401@sss.pgh.pa.us>

* 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