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?
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
