Re: WAL file location

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Cc: PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL file location
Date: 2002-07-30 21:41:41
Message-ID: Pine.LNX.4.44.0207301847580.1928-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Lockhart writes:

> 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".

I'm not in favor of keeping this sort of information in environment
variables or in a command-line option. It should be kept in permanent
storage in the data area. (In other words, it should be stored in a
file.) Consider, tomorrow someone wants to move the commit log or wants
to keep duplicate copies of either log. We should have some extensible
structure in place before we start moving things around.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-07-30 21:42:00 Re: Password sub-process ...
Previous Message Jeff Davis 2002-07-30 21:41:02 Re: Why is MySQL more chosen over PostgreSQL?