| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [[deprecated("don't call this, call that")]] |
| Date: | 2026-04-09 03:42:36 |
| Message-ID: | adcgLAKdTwBeYbjM@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 09, 2026 at 03:34:30PM +1200, Thomas Munro wrote:
> The idea would be to back-patch the deprecation warnings, and delete
> the functions in, I guess now, v20. Then the deprecation notice
> facility would always be there for next time we need it.
That would be a nice addition, especially with the recent mblen()
business (could have used that a few times myself). So +1 for the
addition of the macro in the back branches.
Do we need to be that conservative with the removal in v19? We could
just pull the deletion switch without waiting for v20, IMO.. With the
deprecated macro in place, at least folks would be aware of the
problem.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-04-09 04:09:35 | Re: Logical Replication - revisit `is_table_publication` function implementation |
| Previous Message | shveta malik | 2026-04-09 03:36:21 | Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication |