Re: Autovacuum launcher occurs error when cancelled by SIGINT
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Michael Paquier <michael.paquier@gmail.com>, Kuntal Ghosh <kuntalghosh.2007@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Yugo Nagata <nagata@sraoss.co.jp>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2017-06-22T17:52:54Z
Lists: pgsql-hackers
Thomas Munro wrote: > Hmm. So the problem here is that AutoVacLauncherMain assumes that > there are only two possibilities: (1) there is no handle published in > shmem yet, so we should create a DSA area and publish the handle, and > (2) there is a handle published in shmem so we should attach to it. > But there is a another possiblity: (3) there is a handle published in > shmem, but we are already attached to it (because we've restarted our > main loop after SIGINT). > > The suggestion so far was to check if we're already attached to that > segment (making use of the implementation detail that a DSA handle is > also a DSM segment handle), but don't we know if we're already > attached by checking our AutoVacuumDSA variable? This seems like a good fix to me. Pushed this way, with an additional comment. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix autovacuum launcher attachment to its DSA
- a4f06606a328 10.0 landed