Skip site navigation (1) Skip section navigation (2)

Re: Re: pgsql: add EPERM to the list of return codes to expect from opening

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Greg Stark <gsstark(at)mit(dot)edu>, Greg Stark <stark(at)postgresql(dot)org>, "<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
Date: 2010-03-01 16:30:04
Message-ID: 603c8f071003010830hc740b7fj5353d09e839cf33c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers 
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?

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-03-01 16:31:18
Subject: Re: Linux start script updates
Previous:From: Tom LaneDate: 2010-03-01 16:11:11
Subject: Re: contrib/xml2 regression tests vs no-libxslt build option

pgsql-committers by date

Next:From: Andrew DunstanDate: 2010-03-01 16:40:31
Subject: Re: Re: pgsql: add EPERM to the list of return codes to expect from opening
Previous:From: Magnus HaganderDate: 2010-03-01 16:02:01
Subject: pgsql: It's clearly now pointless to do backwards compatible parsing of

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group