Re: BUG #16632: Not a bug, just a typo - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: BUG #16632: Not a bug, just a typo
Date
Msg-id DF3E9235-1AD8-476C-A82F-F773C2239F1D@yesql.se
Whole thread Raw
In response to BUG #16632: Not a bug, just a typo  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16632: Not a bug, just a typo  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-bugs
> On 24 Sep 2020, at 09:06, PG Bug reporting form <noreply@postgresql.org> wrote:

> In https://www.postgresql.org/developer/roadmap/ it says 'August 12th,
> 2020', should of course be 2021.

Nice catch, thats indeed incorrect.  Since there is a release pending, I don't
want to change anything just now to avoid potential merge conflicts, so CC:ing
Jonathan who can include this fix when suitable.

cheers ./daniel


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16634: Conflicting names of indexes for partitioned tables
Next
From: David Rowley
Date:
Subject: Re: BUG #16627: union all with partioned table yields random aggregate results