Re: Re: pgsql: add EPERM to the list of return codes to expect from opening
| От | Tom Lane |
|---|---|
| Тема | Re: Re: pgsql: add EPERM to the list of return codes to expect from opening |
| Дата | |
| Msg-id | 18562.1267461786@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Re: pgsql: add EPERM to the list of return codes to expect from opening (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: Re: pgsql: add EPERM to the list of return codes to
expect from opening
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, Mar 1, 2010 at 10:01 AM, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-hackers по дате отправления: