Re: XLogDir

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Subject: Re: XLogDir
Date: 2002-08-17 03:55:43
Message-ID: 200208170355.g7H3tho28700@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > A recent change made XLogDir dynamically sized. There was a question of
> > whether this was a good idea since there are lots of other places that
> > use MAXPGPATH.
>
> > I have now found that pg_resetxlog doesn't compile anymore because
> > XLogDir is a char* now instead of a char[].
>
> > Should I fix pg_resetxlog or revert the XLogDir change in the backend.
>
> Revert. The XLogDir change was incomplete and basically useless to
> start with ...

Yea, but it was tied into the PGXLOG commit. Thomas, what are we doing
with that?

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

In response to

Responses

  • Re: XLogDir at 2002-08-20 04:40:52 from Thomas Lockhart

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-08-17 04:16:14 Re: Open 7.3 items
Previous Message Philip Warner 2002-08-17 03:18:02 Function result cacheing