Re: Remove deprecated -H option from oid2name - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Remove deprecated -H option from oid2name
Date
Msg-id 9DF6F2E1-88D3-4129-980D-4ECAA45041EB@yesql.se
Whole thread Raw
In response to Re: Remove deprecated -H option from oid2name  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Remove deprecated -H option from oid2name
Re: Remove deprecated -H option from oid2name
List pgsql-hackers
> On 9 Oct 2024, at 19:15, Nathan Bossart <nathandbossart@gmail.com> wrote:

> Another problem is that "deprecated" may or may not imply that the feature
> will be removed in the future.  IMHO we should be clear about that when we
> intend to remove something down the road (e.g., "this flag is deprecated
> and will be removed in a future major release of PostgreSQL").

That's a fair point, but if we don't aim to remove something we have, IMHO, a
social contract to maintain the feature instead and at that point it's
questionable if it is indeed deprecated.  I guess I think we should separate
between discouraged and deprecated.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: incorrect wal removal due to max_slot_wal_keep_size
Next
From: Paul Ramsey
Date:
Subject: Pg17 Crash in Planning (Arrays + Casting + UDF)