Re: First-draft release notes for back branches are up

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: First-draft release notes for back branches are up
Date: 2019-05-05 04:24:41
Message-ID: CA+hUKG+0BvbdPvb3YLsXLMTV+mPGiaJeArs5yvDVmH=NXYTuDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 5, 2019 at 2:35 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> On 5/3/19 6:29 PM, Tom Lane wrote:
> > See
> >
> > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8b3bce2017b15e05f000c3c5947653a3e2c5a29f
> >
> > Please send any corrections by Sunday.
>
> Attached is a draft of the press release to go out. Please let me know
> if there are any inaccuracies / glaring omissions / awkward language etc.

Hi Jonathan,

> * Relax panics on fsync failures for certain cases where a failure indicated "operation not supported"

Maybe "fsync and sync_file_range". I suspect the latter actually
affected more people, but either way I think we should mention both.

> * Fix handling of lc\_time settings that imply an encoding different from the database's encoding

Maybe this should be marked up as `lc_time` like other
identifier/file/whatever names?

> * Several fixes for `conritb/postgres_fdw`, including one for remote partitions where an UPDATE could lead to incorrect results or a crash

Typo: contrib

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2019-05-05 04:58:21 Re: POC: Cleaning up orphaned files using undo logs
Previous Message Jonathan S. Katz 2019-05-05 02:34:51 Re: First-draft release notes for back branches are up