Re: Do we still need PowerPC-specific timestamp_is_current/epoch?

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: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, lockhart(at)alumni(dot)caltech(dot)edu, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Do we still need PowerPC-specific timestamp_is_current/epoch?
Date: 2001-03-13 15:32:24
Message-ID: 200103131532.KAA12371@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > After further research, I remembered that we used to have "DB_MIN
> > check" in configure back to 6.4.2:
> > I don't know wht it was removed,
>
> Hmm. Digging in the CVS logs shows that it was removed by Bruce in
> configure.in version 1.262, 1999/07/18, with the unedifying log message
> "configure cleanup".
>
> A guess is that he took it out because it wasn't being used anywhere.

Yes, I checked all configure flags and removed the ones not being used.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gunnar R|nning 2001-03-13 15:36:25 Re: Performance monitor
Previous Message Thomas Lockhart 2001-03-13 15:31:02 Re: PostgreSQL on multi-CPU systems