|From:||"Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>|
|To:||Thomas Munro <thomas(dot)munro(at)gmail(dot)com>|
|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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 5/5/19 12:24 AM, Thomas Munro wrote:
> 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:
>>> 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
Thanks! I have made all of those changes.
|Next Message||Tom Lane||2019-05-06 17:32:14||Re: Fixing order of resowner cleanup in 12, for Windows|
|Previous Message||Alvaro Herrera||2019-05-06 16:33:59||Re: make \d pg_toast.foo show its indices ; and, \d toast show its main table|