| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | "Justin Clift" <justin(at)postgresql(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Curt Sampson" <cjs(at)cynic(dot)net>, "PostgreSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PGXLOG variable worthwhile? |
| Date: | 2002-09-17 05:32:23 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOAEEECEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
I personally don't see the problem with a GUC variable...that seems like the
perfect solution to me...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-17 05:36:11 | Re: PGXLOG variable worthwhile? |
| Previous Message | Bruce Momjian | 2002-09-17 05:29:00 | Re: 7.3 Beta Schema and pg_dump |