From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Shay Rojansky <roji(at)roji(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Some 9.5beta2 backend processes not terminating properly? |
Date: | 2015-12-28 23:08:56 |
Message-ID: | 32668.1451344136@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Shay Rojansky <roji(at)roji(dot)org> writes:
> After setting up 9.5beta2 on the Npgsql build server and running the Npgsql
> test suite against I've noticed some weird behavior.
> The tests run for a couple minutes, open and close some connection. With my
> pre-9.5 backends, the moment the test runner exits I can see that all
> backend processes exit immediately, and pg_activity_stat has no rows
> (except the querying one). With 9.5beta2, however, some backend processes
> continue to stay alive beyond the test runner, and pg_activity_stat
> contains extra rows (state idle, waiting false). This situation persists
> until I restart PostgreSQL.
No idea what's happening, but a couple of questions:
* Are you using SSL connections?
* Can you get stack traces from the seemingly-stuck backends?
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2015-12-28 23:30:09 | Re: GIN pending list clean up exposure to SQL |
Previous Message | Peter Geoghegan | 2015-12-28 23:03:25 | Re: Using quicksort for every external sort run |