| From: | Jonathan Rudenberg <jonathan(at)titanous(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Andreas Seltenreich <seltenreich(at)gmx(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Unpinning error in parallel worker |
| Date: | 2018-04-17 20:52:31 |
| Message-ID: | 1523998351.1231357.1341528496.28EBAF7F@webmail.messagingengine.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 29, 2017, at 10:50, Robert Haas wrote:
> On Wed, Mar 29, 2017 at 1:31 AM, Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> > I considered whether the error message could be improved but it
> > matches the message for an existing similar case (where you try to
> > attach to an unknown handle).
>
> Ugh, OK. I committed this, but I think this whole file needs a visit
> from the message style police.
I ran into an issue that matches the symptoms of this bug on a production cluster running 10.3 (Ubuntu 10.3-1.pgdg16.04+1) twice in the past week.
Hundreds of queries stuck with a wait_event of DynamicSharedMemoryControlLock and pg_terminate_backend did not terminate the queries.
In the log:
> FATAL: cannot unpin a segment that is not pinned
I don't have a backtrace yet, but I will provide them if/when the issue happens again.
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-04-17 21:19:53 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Alvaro Herrera | 2018-04-17 20:18:50 | Re: partitioning code reorganization |