From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | 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:00:11 |
Message-ID: | 20150726150011.GA12755@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2015-07-26 15:01:50 | Re: checkpointer continuous flushing |
Previous Message | Joe Conway | 2015-07-26 14:59:30 | Re: A little RLS oversight? |