On Sat, Apr 16, 2016 at 03:28:23PM -0700, Andres Freund wrote: > On 2016-04-16 18:23:01 -0400, Noah Misch wrote: > > On Tue, Apr 12, 2016 at 09:00:57AM -0400, Robert Haas wrote: > > > On Mon, Apr 11, 2016 at 1:17 PM, Andres Freund <and...@anarazel.de> wrote: > > > > I can think of a number of relatively easy ways to address this: > > > > 1) Just zap (or issue?) all pending flush requests when getting an > > > > smgrinval/smgrclosenode > > > > 2) Do 1), but filter for the closed relnode > > > > 3) Actually handle the case of the last open segment not being > > > > RELSEG_SIZE properly in _mdfd_getseg() - mdnblocks() does so. > > > > > > > > I'm kind of inclined to do both 3) and 1). > > > > Andres, you own the underlying open item, right? > > Right. > > > Do you plan to implement this fix you have outlined? If so, when? > > Yes, I plan to next week.
Completion by the end of next week will work. Thanks. At that time (2016-04-24T00:00 UTC), this would otherwise have spent twenty-three days as an open item. Would you inform this thread if you discover reasons to think your plan will no longer succeed? -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
