Re: Remove deprecated -H option from oid2name
От | Peter Eisentraut |
---|---|
Тема | Re: Remove deprecated -H option from oid2name |
Дата | |
Msg-id | c98d45c5-8ee6-42a0-93e7-b4542d287bcf@eisentraut.org обсуждение исходный текст |
Ответ на | Re: Remove deprecated -H option from oid2name (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: Remove deprecated -H option from oid2name
|
Список | pgsql-hackers |
On 09.10.24 20:30, Daniel Gustafsson wrote: >> 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. The dictionary definition of "deprecate" is "to express disapproval of", which I think is about the same as your "discouraged". If we need another term, then we should say something like "planned/scheduled to be removed".
В списке pgsql-hackers по дате отправления: