Re: potential stuck lock in SaveSlotToPath()
От | Alvaro Herrera |
---|---|
Тема | Re: potential stuck lock in SaveSlotToPath() |
Дата | |
Msg-id | 20200318195419.GA7549@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: potential stuck lock in SaveSlotToPath() (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: potential stuck lock in SaveSlotToPath()
|
Список | pgsql-hackers |
On 2020-Mar-18, Andres Freund wrote: > Hi, > > On 2020-03-18 16:46:23 +0100, Peter Eisentraut wrote: > > When SaveSlotToPath() is called with elevel=LOG, the early exits don't > > release the slot's io_in_progress_lock. Fix attached. > > I'm a bit confused as to why we we ever call it with elevel = LOG > (i.e. why we have the elevel parameter at all). That seems to have been > there from the start, so it's either me or Robert that's to blame. But I > can't immediately see a reason for it? I guess you didn't want failure to save a slot be a reason to abort a checkpoint. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: