Re: PGXLOG variable worthwhile? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PGXLOG variable worthwhile?
Date
Msg-id 200209170519.g8H5Jcn27654@candle.pha.pa.us
Whole thread Raw
In response to PGXLOG variable worthwhile?  (Justin Clift <justin@postgresql.org>)
Responses Re: PGXLOG variable worthwhile?  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
Robert Treat wrote:
> It seems all of this discussion misses the point. Either it has a large
> amount of impact and the idea gets rejected because of implementation
> issues, or it has little impact but it's nothing the core group wants to
> implement. If the problem is finding someone to implement it, it sounds
> like Justin has found such a person, so are we going to stand in his way
> while we wax poetic about OS religion and corporate philosophies or can
> he start submitting patches?

Actually, the work is minimal.  Look at the commit I used to remove
PGXLOG, trim that to remove the changes to make the path name dynamic in
size (added too much complexity for little benefit) and hang the path
coding off a GUC variable rather than an environment variable.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: attlognum
Next
From: Bruce Momjian
Date:
Subject: Re: 7.3 Beta Schema and pg_dump