WAL file location - Mailing list pgsql-hackers

From Thomas Lockhart
Subject WAL file location
Date
Msg-id 3D45F1CE.D3A3A4FF@fourpalms.org
Whole thread Raw
Responses Re: WAL file location  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: WAL file location  (Curt Sampson <cjs@cynic.net>)
Re: WAL file location  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
I've developed patches to be able to specify the location of the WAL
directory, with the default location being where it is now. The patches
define a new environment variable PGXLOG (a la PGDATA) and postmaster,
postgres, initdb and pg_ctl have been taught to recognize a new command
line switch "-X" a la "-D".

Comments or suggestions?

I'm intending to head towards finer control of locations of tables and
indices next by implementing some notion of named storage area, perhaps
including the "tablespace" nomenclature though it would not be the same
thing as in Oracle since it would not be fixed size but more akin to the
"secondary locations" that we support now for entire databases.

There has been some discussion of this already but I'm not recalling
that someone has picked this up yet. Comments or suggestions?
                 - Thomas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: No bison and NAMEDATALEN > 31: initdb failure?
Next
From: "Christopher Kings-Lynne"
Date:
Subject: CVS server munted