Re: Re: pgsql: add EPERM to the list of return codes to expect from opening
From:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:
Robert Haas <robertmhaas(at)gmail(dot)com>
Cc:
Magnus Hagander <magnus(at)hagander(dot)net>, Greg Stark <gsstark(at)mit(dot)edu>,
Andrew Dunstan <andrew(at)dunslane(dot)net>,
"<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org>
Subject:
Re: Re: pgsql: add EPERM to the list of return codes to expect from opening
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Mar 1, 2010 at 10:01 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> BTW, in case anyone with admin privileges is paying attention, the
>> buildfarm (a) is about two hours off on its system clock again,
>> and (b) hasn't sent out a daily status-change summary email since
>> Friday.
> Eh? The buildfarm sends out a daily status-change summary email? To where?
See
http://pgfoundry.org/mail/?group_id=1000040
I'm subscribed to pgbuildfarm-status-green ... and the archives for
it match my local log, which says there hasn't been a message since
Friday. That's definitely not for lack of changes. Now that I look
at the archives, it looks like all the status lists stopped getting
mail around that time.
regards, tom lane
