| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First-draft release notes for next week's releases |
| Date: | 2019-02-09 02:10:02 |
| Message-ID: | CAH2-Wz=7dBVffWCH_2+G+s71ZBd15BM3=GwmWx_=MUG0VJN13A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 8, 2019 at 6:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yeah, I saw that in the commit message, but didn't really think that
> the release note entry needed to explain it that way. Could be
> argued differently though.
I'm pretty confident that somebody is going to miss this
functionality, if this account of how the patch helped Yandex is
anything to go by:
https://www.postgresql.org/message-id/7B44397E-5E0A-462F-8148-1C444640FA0B%40simply.name
> > We may even need to revise the v10 release notes.
>
> Perhaps just remove that item from the 10.0 notes?
The wording could be changed to reflect the current reality within
GIN. It's still useful that posting trees are only locked when there
are pages to be deleted.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-02-09 04:08:07 | Re: First-draft release notes for next week's releases |
| Previous Message | Tom Lane | 2019-02-09 02:00:08 | Re: First-draft release notes for next week's releases |