Re: Retiring some encodings?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Bruce Momjian <bruce(at)momjian(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Retiring some encodings?
Date: 2025-05-23 08:21:42
Message-ID: B42307F7-B6DF-468E-8B1A-0D7C0B062E02@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 23 May 2025, at 09:18, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:

> If we plan to remove something in the future, I think putting a deprecation notice in the docs in v18 is still a good idea. There's no point in hiding the plan by not documenting it sooner. The more advance notice people get the better.

+1

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Feike Steenbergen 2025-05-23 08:43:06 pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Previous Message Heikki Linnakangas 2025-05-23 08:10:47 Re: Enable data checksums by default