On Thu, Apr 04, 2019 at 09:25:12AM +0900, Kyotaro HORIGUCHI wrote:
Hello.
At Wed, 3 Apr 2019 12:56:59 -0700, Andres Freund <and...@anarazel.de> wrote in
<20190403195659.fcmk2i7ruxhty...@alap3.anarazel.de>
Unfortunately I don't think it's realistic to target this to v12. I
think it was unlikely to make at the beginning of the CF, but since then
development just wasn't quick enough to warrant aiming for it. It's a
large and somewhat complex patch, and has some significant risks
associated. Therefore I think we should mark this as targeting v13, and
move to the next CF?
I'd like to get this in 12 but actually the time is coming. If
everyone think that that is not realistic, I do that.
Unfortunately, now that we're past code freeze it's clear this is a PG12
matter now :-(
I personally consider this to be very worthwhile & beneficial improvement,
but I agree with Andres the patch did not quite get to committable state
in the last CF. Conidering how sensitive part it touches, I suggest we try
to get it committed early in the PG13 cycle. I'm willing to spend some
time on doing test/benchmarks and reviewing the code, if needed.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
