Re: Buildfarm failure from overly noisy warning message - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Buildfarm failure from overly noisy warning message
Date
Msg-id 20150726150011.GA12755@awork2.anarazel.de
Whole thread Raw
In response to Buildfarm failure from overly noisy warning message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Buildfarm failure from overly noisy warning message
List pgsql-hackers
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.


- Andres



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: A little RLS oversight?
Next
From: Fabien COELHO
Date:
Subject: Re: checkpointer continuous flushing