pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: David Steele <david@pgmasters.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Haribabu Kommi <kommi.haribabu@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Pluggable storage
Date: Thu, 29 Mar 2018 09:07:06 -0400
Message-ID: <a1c4e8b0-c98a-8351-38e7-133bd2c438d2@pgmasters.net> (raw )
In-Reply-To: <20180329003944.GG2102@paquier.xyz >
References: <CAPpHfdtF3=aN2Knis+ZnbDYrZYJROesxLhbc5U3c0HCnYp4g1g@mail.gmail.com >
<CAJrrPGeoihBWs+BUP06q9=rCNm75m56J-EEStf3ygikNcpreYw@mail.gmail.com >
<CA+TgmoY0qnoRCRWX20LmnUrHhpJsaMCnO59N6FEYvKn-q2Zsyg@mail.gmail.com >
<CAPpHfdvYX7NTq=PpO4oUsitXeFnRKsnvp2Api7i+u2xBOwxKvQ@mail.gmail.com >
<CAJrrPGdY_hgvu06R_vCibUktKRLp=b8nBfeZkh=KRc95tq4euA@mail.gmail.com >
<CAJrrPGcJsqjBJh5zPGveW8B8qz-6wMQfqn2rtH-T6ThBHJ6YdQ@mail.gmail.com >
<CAPpHfdvZpxxwcP1LMXveUT5F0-8aCG+jSKQ-qBH5V_ykipuMEQ@mail.gmail.com >
<CA+Tgmobg1A57qkMqyycoRUN1QhvP8G+9Ms=+uB1Mvfjf08oXNA@mail.gmail.com >
<CAPpHfdueaQ=C0xVZxkOzCyhZGHMRtExckvh+vkGSLA3WCAx8Dg@mail.gmail.com >
<935d4bc2-936e-73ff-b242-d2e8ebfc5d55@pgmasters.net >
<20180329003944.GG2102@paquier.xyz >
On 3/28/18 8:39 PM, Michael Paquier wrote:
> On Wed, Mar 28, 2018 at 12:23:56PM -0400, David Steele wrote:
>> I think this entry should be moved the the next CF. I'll do that
>> tomorrow unless there are objections.
>
> Instead of moving things to the next CF by default, perhaps it would
> make more sense to mark things as reviewed with feedback as this is the
> last CF? There is a 5-month gap between this commit fest and the next
> one, I am getting afraid of flooding the beginning of v12 development
> cycle with entries which keep rotting over time. If the author(s) claim
> that they will be able to work on it, then that's of course fine.
I agree and I do my best to return patches that have stalled, but I
don't think this patch is in that category. It has gotten review and
has been kept up to date. I don't think it's a good fit for v11 but I'd
like to see it in the first CF for v12.
> Sorry for the digression, patches ignored across CFs contribute to the
> bloat we see, and those eat the time of the CFM.
There's no question that bloat has become a problem. I don't have all
the answers, but vigilance by the CFMs is certainly a good start.
Regards,
--
-David
david@pgmasters.net
Attachments:
[application/pgp-signature] signature.asc (873B, ../a1c4e8b0-c98a-8351-38e7-133bd2c438d2@pgmasters.net/2-signature.asc)
download
view thread (138+ messages) latest in thread
Message-ID: <a1c4e8b0-c98a-8351-38e7-133bd2c438d2@pgmasters.net>
Permalink: ../a1c4e8b0-c98a-8351-38e7-133bd2c438d2@pgmasters.net/
Also on: postgresql.org/message-id/a1c4e8b0-c98a-8351-38e7-133bd2c438d2@pgmasters.net
copy link · copy postgr.es
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: david@pgmasters.net, michael@paquier.xyz, a.korotkov@postgrespro.ru, robertmhaas@gmail.com, kommi.haribabu@gmail.com, michael.paquier@gmail.com, amit.kapila16@gmail.com, thomas.munro@enterprisedb.com, alvherre@2ndquadrant.com
Subject: Re: [HACKERS] Pluggable storage
In-Reply-To: <a1c4e8b0-c98a-8351-38e7-133bd2c438d2@pgmasters.net>
* 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