> Can someone test this in a bulk? Also, OKs to apply this if no fallout
> from the bulk?
No fallout.
ok tb
Le Mon, Nov 27, 2023 at 08:11:18PM +, Jeremy Evans a écrit :
>
> databases/timescaledb version
>
> PostgreSQL 16 support not yet ready, planned for future version. I
> marked it BROKEN, same as in the last 2 PostgreSQL major upgrades.
>
A new version was released today with suppo
On 09/16 09:56, Theo Buehler wrote:
> On Thu, Sep 14, 2023 at 06:06:37PM +, Jeremy Evans wrote:
> > PostgreSQL 16.0 was released today:
> > https://www.postgresql.org/about/news/postgresql-16-released-2715/
> >
> > As usual, we don't plan to change the default version in ports until
> > 16.1,
On 2023/09/17 00:11, Jeremy Evans wrote:
> On 09/16 09:56, Theo Buehler wrote:
> > On Thu, Sep 14, 2023 at 06:06:37PM +, Jeremy Evans wrote:
> > > PostgreSQL 16.0 was released today:
> > > https://www.postgresql.org/about/news/postgresql-16-released-2715/
> > >
> > > As usual, we don't plan to
On 09/16 09:56, Theo Buehler wrote:
> On Thu, Sep 14, 2023 at 06:06:37PM +, Jeremy Evans wrote:
> > PostgreSQL 16.0 was released today:
> > https://www.postgresql.org/about/news/postgresql-16-released-2715/
> >
> > As usual, we don't plan to change the default version in ports until
> > 16.1,
On Thu, Sep 14, 2023 at 06:06:37PM +, Jeremy Evans wrote:
> PostgreSQL 16.0 was released today:
> https://www.postgresql.org/about/news/postgresql-16-released-2715/
>
> As usual, we don't plan to change the default version in ports until
> 16.1, and after we have prepared updates all software
PostgreSQL 16.0 was released today:
https://www.postgresql.org/about/news/postgresql-16-released-2715/
As usual, we don't plan to change the default version in ports until
16.1, and after we have prepared updates all software that depends on
PostgreSQL to support the new version. However, for ear
