Re: Strange failure in LWLock on skink in REL9_5_STABLE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Strange failure in LWLock on skink in REL9_5_STABLE
Date
Msg-id 28445.1537502799@sss.pgh.pa.us
Whole thread Raw
In response to Re: Strange failure in LWLock on skink in REL9_5_STABLE  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: Strange failure in LWLock on skink in REL9_5_STABLE  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
Thomas Munro <thomas.munro@enterprisedb.com> writes:
> ... There may be ways to fix the dsm_resize() path
> based on the observation that you don't need to fallocate() if you
> made the mapping smaller, and if you made it bigger then you could
> always undo that on error (or not) and you haven't thrown away any
> data.  Hmm... I note that there are actually no callers of
> dsm_resize(), and it's not implemented on Windows or SystemV.

Why would we fix it rather than just removing it?

            regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Problem while setting the fpw with SIGHUP
Next
From: Andres Freund
Date:
Subject: Re: Strange failure in LWLock on skink in REL9_5_STABLE