pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Koczan <pjkoczan@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: best practices for separating data and logs
Date: Wed, 2 Jan 2008 11:46:15 -0600
Message-ID: <4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.com> (raw)

Hi all,

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?

- 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 searched through the archives and found a few threads regarding
separating data and WAL, but nothing regarding best practices or
specifics.

Thanks,
Peter

P.S. Here are exact details on how I have things set up.

[root@mitchell testing-8.2]# pwd
/scratch.1/postgres/testing-8.2

[root@mitchell testing-8.2]# ls -l
total 48
drwx------ 8 postgres postgres    83 Oct  8 16:57 base
drwx------ 2 postgres postgres  4096 Oct 12 05:07 global
drwx------ 2 postgres postgres    94 Oct  9 14:28 pg_clog
-rw------- 1 postgres postgres  3841 Aug 28 14:16 pg_hba.conf
-rw------- 1 postgres postgres  1460 Aug  8 14:06 pg_ident.conf
drwx------ 4 postgres postgres    34 Aug  8 14:06 pg_multixact
drwx------ 2 postgres postgres    17 Oct 12 00:15 pg_subtrans
drwx------ 2 postgres postgres     6 Aug  8 14:06 pg_tblspc
drwx------ 2 postgres postgres     6 Aug  8 14:06 pg_twophase
-rw------- 1 postgres postgres     4 Aug  8 14:06 PG_VERSION
lrwxrwxrwx 1 root     root        37 Oct  8 16:18 pg_xlog ->
/scratch/postgres/testing-8.2/pg_xlog
-rwxr-xr-x 1 postgres postgres 15212 Oct 11 15:05 postgresql.conf
-rw------- 1 postgres postgres    96 Oct 11 15:55 postmaster.opts
-rw------- 1 postgres postgres    57 Oct 11 15:55 postmaster.pid
-rw-r--r-- 1 postgres postgres  1805 Aug  8 14:06 server.crt
-rw------- 1 postgres postgres  1675 Aug  8 14:06 server.key

[root@mitchell testing-8.2]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1              1019208    434264    532336  45% /
/dev/sda8             56394768    348344  53135448   1% /scratch
/dev/sda6              1019208     34664    931936   4% /tmp
/dev/sda3              4061572    202080   3649844   6% /var
/dev/sda7              1019208    701972    264628  73% /var/vice/cache
/dev/sda2             10154020   5616776   4013124  59% /usr
tmpfs                   451556         0    451556   0% /dev/shm
/dev/sdb1             78110004   9589792  68520212  13% /scratch.1
AFS                    9000000         0   9000000   0% /afs



view thread (4+ messages)  latest in thread

Message-ID: <4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.com>
Permalink:  ../4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.com/
Also on:    postgresql.org/message-id/4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.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-admin@postgresql.org
  Cc: pjkoczan@gmail.com
  Subject: Re: best practices for separating data and logs
  In-Reply-To: <4544e0330801020946i314c0c8n5830dcc4512849ee@mail.gmail.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