I have written, what service stopped. This action is repeatable.
You can run command 'psql -c "do $$ unpack p,1x8 $$ language plperlu;"'
and after this windows service will stop.
On Сб, 2015-10-10 at 10:23 -0500, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Fri, Oct 9, 2015 at 5:52 AM, Dmitry Vasilyev
> > > postgres=# select 1;
> > > server closed the connection unexpectedly
> > > This probably means the server terminated abnormally
> > > before or while processing the request.
> > > The connection to the server was lost. Attempting reset: Failed.
>
> > Hmm. I'd expect that to cause a crash-and-restart cycle, just like
> > a
> > SIGQUIT would cause a crash-and-restart cycle on Linux. But I
> > would
> > expect the server to end up running again at the end, not stopped.
>
> It *is* a crash and restart cycle, or at least no evidence to the
> contrary has been provided.
>
> Whether psql's attempt to do an immediate reconnect succeeds or not
> is
> very strongly timing-dependent, on both Linux and Windows. It's easy
> for it to attempt the reconnection before crash recovery is complete,
> and then you get the above symptom. Personally I get a "Failed"
> result
> more often than not, regardless of platform.
>
> regards, tom lane