Postgres Pro
Downloads
Home   >   mailing lists

potential stuck lock in SaveSlotToPath() - Mailing list pgsql-hackers

From Peter Eisentraut
Subject potential stuck lock in SaveSlotToPath()
Date
Msg-id 56a138c5-de61-f553-7e8f-6789296de785@2ndquadrant.com
Whole thread Raw
Responses Re: potential stuck lock in SaveSlotToPath()  (Andres Freund <andres@anarazel.de>)
Re: potential stuck lock in SaveSlotToPath()  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Tree view 
When SaveSlotToPath() is called with elevel=LOG, the early exits don't 
release the slot's io_in_progress_lock.  Fix attached.

This could result in a walsender being stuck on the lock forever.  A 
possible way to get into this situation is if the offending code paths 
are triggered in a low disk space situation.  (This is how it was found; 
maybe there are other ways.)

Pavan Deolasee and Craig Ringer worked on this issue.  I'm forwarding it 
on their behalf.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side
Next
From: Tomas Vondra
Date:
Subject: Re: Multivariate MCV list vs. statistics target