From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Wayne Pichotta <wpichotta(at)truecar(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: postmaster became multithreaded |
Date: | 2017-03-28 20:32:44 |
Message-ID: | 25424.1490733164@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Wayne Pichotta <wpichotta(at)truecar(dot)com> writes:
> I just saw this in my logs:
> LOG: postmaster became multithreaded
> DETAIL: Please report this to <pgsql-bugs(at)postgresql(dot)org>.
Just reporting the bare fact of that message isn't helpful.
The known causes of that involve doing something thread-oriented
in an "unsafe" language such as pltclu, plperlu, or plpythonu,
or perhaps bare C --- and even then, you'd have had to go well out
of your way to make it happen in the postmaster process
instead of some child process.
However, you haven't told us what nondefault configuration you
might be using, or what platform this is on, or even what PG version
it is. So it's impossible to speculate further.
FWIW, that's only an informational log message emitted during a
postmaster shutdown that occurred for some other reason. Maybe
it's related to the reason, but again we have zero info. Preceding
lines in the log might have provided some knowledge.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-03-28 20:40:48 | Re: BUG #14601: Alternative support for amcanorder column under pg_am |
Previous Message | Prajval Poojari | 2017-03-28 20:32:23 | Re: BUG #14601: Alternative support for amcanorder column under pg_am |