Re: [COMMITTERS] pgsql: Do missed autoheader run for previous commit.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Do missed autoheader run for previous commit.
Date: 2011-11-18 14:54:23
Message-ID: 15647.1321628063@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of vie nov 18 11:12:32 -0300 2011:
>>> Hmm, does the win32 file need updating too?

>> I don't see HAVE_SCANDIR in there, do you?

> Well, I wonder if the win32 file needs to be hooked to the whole
> autoconf/autoheader thing somehow. I mean, if HAVE_SCANDIR wasn't
> there, does this mean that when it was added to pg_config.h we forgot to
> update the win32 copy?

Well, it might mean that, or it might mean that somebody intentionally
didn't bother to add the symbol because Windows hasn't got the function.

Yeah, it would be nice if autoconf worked for Windows ...

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2011-11-18 16:09:57 pgsql: Avoid marking buffer dirty when VACUUM has no work to do.
Previous Message Alvaro Herrera 2011-11-18 14:24:35 Re: pgsql: Do missed autoheader run for previous commit.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-11-18 14:55:49 Re: VACUUM touching file but not updating relation
Previous Message Tom Lane 2011-11-18 14:47:18 Re: VACUUM touching file but not updating relation