Re: 2019-03 CF Summary / Review - Tranche #2

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 2019-03 CF Summary / Review - Tranche #2
Date: 2019-02-18 05:15:46
Message-ID: CAKJS1f9_kOkE-5oF6YG=g=HAs6+Np8qcAEWBfDcFwUz88FPA6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 18 Feb 2019 at 15:50, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> On 2019/02/18 11:13, Tsunakawa, Takayuki wrote:
> > From: Andres Freund [mailto:andres(at)anarazel(dot)de]
> >> - Speed up planning with partitions
> >>
> >> NR: Important feature, but based on a skim of the discussion this
> >> doesn't seem ready for v12.
> >>
> >> Andres: punt to v13
> >
> >> - Speed up transaction completion faster after many relations are
> >> accessed in a transaction
> >>
> >> NR: This has only been submitted 2019-02-12. While not a really
> >> complicated patch, it's also not trivial. Therefore I'd say this falls
> >> under our policy of not merging nontrivial patches first submitted to
> >> the last CF.
> >>
> >> Andres: punt to v13
> >
> > I hope these will be continued in PG 12, because these will make PostgreSQL comparable to a commercial database in OLTP workloads. I'd like to hear from Amit and David on the feasibility.
>
> As far as the first one is concerned (speed up planning with partitions),
> although there's no new functionality [1], there is quite a bit of code
> churn affecting somewhat complex logic of inheritance planning.

I think we need to treat each patch in that series individually. Last
time I looked, the first 1 or 2 patches looked very close. I know
there's some tricky stuff in later patches in the series, but I don't
think that should stop earlier patches being committed for PG12.
However, I'd say that if the entire thing is to make PG12 then we'll
need to start ticking off earlier patches pretty soon, likely before
March.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-02-18 05:25:03 Re: [Patch] checksumming-related buglets in pg_verify_checksums/pg_basebackup TAP tests
Previous Message David Steele 2019-02-18 05:13:21 Re: Remove Deprecated Exclusive Backup Mode