| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: assert in nested SQL procedure call in current HEAD |
| Date: | 2018-06-29 13:35:43 |
| Message-ID: | 11f6809e-17f2-dea7-a16b-4a262da2bef5@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12.06.18 18:47, Andrew Gierth wrote:
> While testing this, I ran into another semi-related issue:
> shmem_exit_inprogress isn't ever being cleared in the postmaster, which
> means that if you ever have a crash-restart, any attempt to do a
> rollback in a procedure will then crash or get some other form of
> corruption again every time until you manually restart the cluster.
I think we could unset shmem_exit_inprogress at the end of shmem_exit().
I'm trying to remember why we didn't just use proc_exit_inprogress for
this. I'll need to test this more.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-06-29 13:39:00 | Re: Monitoring time of fsyncing WALs |
| Previous Message | Konstantin Knizhnik | 2018-06-29 13:26:34 | Re: Monitoring time of fsyncing WALs |