From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: zheap: a new storage format for PostgreSQL |
Date: | 2018-03-02 09:34:10 |
Message-ID: | CAA4eK1KSESJf1MU6e=p1sRRepY+7VbmV3B+THMZNSF+Mnuz+vg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 2, 2018 at 9:23 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> I think it was impolite to post this on the very same day the commitfest
> started. We have enough patches as it is ...
>
I can understand your concern, but honestly, I have no intention to
hinder the current commit fest work. We are preparing to post this
for more than a month, but it took some time to finish the
documentation and to fix some other issues. I could have posted this
after the CF as well, but I was not sure if there is any benefit in
delaying, because, at this stage, we are not expecting much of code
review, but some feedback on high-level design and I think it can
certainly help pluggable API project. I think the chances of getting
pluggable API in this release is remote, but maybe we can get some
small portion of it.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2018-03-02 09:34:48 | Re: zheap: a new storage format for PostgreSQL |
Previous Message | Arthur Zakirov | 2018-03-02 09:33:30 | Re: [HACKERS] Bug in to_timestamp(). |