Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.c backe ... - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.c backe ...
Date
Msg-id 200208041421.g74ELxs06537@candle.pha.pa.us
Whole thread Raw
Responses Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.c backe ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Thomas Lockhart wrote:
> CVSROOT:    /cvsroot
> Module name:    pgsql-server
> Changes by:    thomas@postgresql.org    02/08/04 02:26:38
> 
> Modified files:
>     src/backend/tcop: postgres.c 
>     src/backend/bootstrap: bootstrap.c 
>     src/backend/postmaster: postmaster.c 
>     src/bin/initdb : initdb.sh 
>     src/bin/pg_ctl : pg_ctl.sh 
>     src/include/access: xlog.h 
> 
> Log message:
>     Implement WAL log location control using "-X" or PGXLOG.

Woh, I didn't think we had agreement on this.  This populates the 'X'
all over the system (postgres, postmaster, initdb, pg_ctl),  while the
simple solution would be to add the flag only to initdb and use a
symlink from /data.  I also think it is less error-prone because you
can't accidentally point to the wrong XLOG directory.  In fact, you
almost have to use an environment variable unles you plan to specify -X
for all the commands.   In my mind, PGDATA should take care of the whole
thing for pointing to your data.

If you want to do it this way, I request a vote.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: fate of CLUSTER command ?
Next
From: Thomas Lockhart
Date:
Subject: Re: Did someone break CVS?