Re: Buildfarm failure from overly noisy warning message

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Buildfarm failure from overly noisy warning message
Date: 2015-07-26 15:29:03
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 07/26/2015 11:00 AM, Andres Freund wrote:
> Hi,
> On 2015-07-26 10:56:05 -0400, Tom Lane wrote:
>> CREATE INDEX tenk2_unique1 ON tenk2 USING btree(unique1 int4_ops);
>> + WARNING: could not send signal to process 30123: No such process
>> What's evidently happened here is that our session tried to boot an
>> autovacuum process off a table lock, only that process was gone by the
>> time we issued the kill() call. No problem really ... but aside from
>> causing buildfarm noise, I could see somebody getting really panicky
>> if this message appeared on a production server.
> Oops.
>> I'm inclined to reduce the WARNING to LOG
> Hm, that doesn't seem like a very nice solution, given that LOG is even
> more likely to end up in the server log.
>> and/or skip it altogether if the error is ESRCH.
> Combined with a comment why we're ignoring that case that'd work for me.

+1 for this. if the process is gone we shouldn't really have a problem,
should we?



In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-07-26 15:36:24 Re: anole: assorted stability problems
Previous Message Heikki Linnakangas 2015-07-26 15:24:31 Re: Sharing aggregate states between different aggregate functions