pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Noah Misch <noah@leadboat.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: robertmhaas@gmail.com
Cc: pgsql-hackers@postgresql.org
Cc: 9erthalion6@gmail.com
Cc: andrew.dunstan@2ndquadrant.com
Cc: hlinnaka@iki.fi
Subject: Re: [HACKERS] WAL logging problem in 9.4.3?
Date: Mon, 30 Mar 2020 23:28:54 -0700
Message-ID: <20200331062854.GC3354091@rfd.leadboat.com> (raw)
In-Reply-To: <20200330074300.GD43995@paquier.xyz>
References: <20200316034647.GA1121601@rfd.leadboat.com>
	<20200321190127.GA1763544@rfd.leadboat.com>
	<20200321224920.GB1763544@rfd.leadboat.com>
	<20200323.172027.2270553329883636814.horikyota.ntt@gmail.com>
	<20200330044101.GA2324620@rfd.leadboat.com>
	<20200330074300.GD43995@paquier.xyz>

On Mon, Mar 30, 2020 at 04:43:00PM +0900, Michael Paquier wrote:
> On Sun, Mar 29, 2020 at 09:41:01PM -0700, Noah Misch wrote:
> > I think attached v41nm is ready for commit.  Would anyone like to vote against
> > back-patching this?  It's hard to justify lack of back-patch for a data-loss
> > bug, but this is atypically invasive.  (I'm repeating the question, since some
> > folks missed my 2020-02-18 question.)  Otherwise, I'll push this on Saturday.
> 
> The invasiveness of the patch is a concern.  Have you considered a
> different strategy?  For example, we are soon going to be in beta for
> 13, so you could consider committing the patch only on HEAD first.
> If there are issues to take care of, you can then leverage the beta
> testing to address any issues found.  Finally, once some dust has
> settled on the concept and we have gained enough confidence, we could
> consider a back-patch.

No.  Does anyone favor this proposal more than back-patching normally?





view thread (244+ messages)  latest in thread

Message-ID: <20200331062854.GC3354091@rfd.leadboat.com>
Permalink:  ../20200331062854.GC3354091@rfd.leadboat.com/
Also on:    postgresql.org/message-id/20200331062854.GC3354091@rfd.leadboat.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: noah@leadboat.com, michael@paquier.xyz, horikyota.ntt@gmail.com, robertmhaas@gmail.com, 9erthalion6@gmail.com, andrew.dunstan@2ndquadrant.com, hlinnaka@iki.fi
  Subject: Re: [HACKERS] WAL logging problem in 9.4.3?
  In-Reply-To: <20200331062854.GC3354091@rfd.leadboat.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox