| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove deprecated -H option from oid2name |
| Date: | 2024-10-09 18:30:20 |
| Message-ID: | 9DF6F2E1-88D3-4129-980D-4ECAA45041EB@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 9 Oct 2024, at 19:15, Nathan Bossart <nathandbossart(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Ramsey | 2024-10-09 18:52:25 | Pg17 Crash in Planning (Arrays + Casting + UDF) |
| Previous Message | Jeff Janes | 2024-10-09 17:29:53 | incorrect wal removal due to max_slot_wal_keep_size |