On 23/05/2025 05:11, Michael Paquier wrote:
> On Thu, May 22, 2025 at 10:02:16AM -0400, Bruce Momjian wrote:
>> Agreed on notification. A radical idea would be to add a warning for
>> the use of such encodings in PG 18, and then mention their deprecation
>> in the PG 18 release notes so everyone is informed they will be removed
>> in PG 19.
>
> With v18beta1 already out in the wild, I think that we are too late
> for taking any action on this version at this stage. Putting a
> deprecation notice for a selected set of conversions and/or encodings
> and do the actual removal work when v20 opens up around July 2026
> would sound like a better timing here, if the overall consensus goes
> in this direction, of course.
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.
--
Heikki Linnakangas
Neon (https://neon.tech)
