On Thu, May 20, 2010 2:12 pm, Tom Lane wrote:
> It's annoying though that
> the buildfarm script didn't capture the relevant log file in this
> particular failure case. Andrew, can we get that fixed?
>
It was captured, but apparently had no new content - not surprising if it
ran out of space.
c
On May 20, 2010, at 11:54 AM, Tom Lane wrote:
> Robert Creager writes:
>> If anyone is interested, I think this failure was accompanied by the
>> following:
>> [ apparent PANIC in UpdateControlFile ]
>
> Hmm, do you have the panic message in the postmaster log? So far as I
> can tell, the pos
Robert Creager writes:
> On May 20, 2010, at 11:54 AM, Tom Lane wrote:
>> Was there any special environment here, like running out of disk space?
> Not that I'm aware of. I did empty trash sometime yesterday after noticing I
> was around 1Gb of free disk. Not sure if that correlates or not. M
Robert Creager writes:
> If anyone is interested, I think this failure was accompanied by the
> following:
> [ apparent PANIC in UpdateControlFile ]
Hmm, do you have the panic message in the postmaster log? So far as I
can tell, the postmaster log isn't captured anywhere in the buildfarm
report
If anyone is interested, I think this failure was accompanied by the following:
Process: postgres [35159]
Path:
/usr/local/src/build-farm-3.2_llvm/builds/HEAD/inst/bin/postgres
Identifier: postgres
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process:
