| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: mention unused_oids script in pg_proc.dat |
| Date: | 2025-05-24 00:47:21 |
| Message-ID: | aDEXGVhL4ZyN3-Fr@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 23, 2025 at 07:03:31PM +0300, Florents Tselai wrote:
> -
For the sake of the archives: this has been mentioned on Discord.
+++ b/src/include/catalog/pg_proc.dat
+# To find unused OIDs see src/include/catalog/unused_oids.
+# If multiple related OIDs are added, it is suggested they're contiguous.
This stuff is already documented in bki.sgml. Adding an extra
location to hint about the script may be useful to have, but
pg_proc.dat is not a good choice as it is one catalog among many
others. One idea: we could add a README or a README.oid in
src/include/catalog/ telling more about unused_oids, renumber_oids and
duplicate_oids, still it would be a duplication of what the
documentation already informs about. Another idea could be just to
provide a link redirecting to the "current" or "in-development" docs,
stored in a README in src/include/catalog/.
The issue seems to be the discoverability of these scripts for new
developers. If others have ideas and/or opinions, feel free.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-05-24 01:05:47 | Re: queryId constant squashing does not support prepared statements |
| Previous Message | Michael Paquier | 2025-05-24 00:37:30 | Re: Random subscription 021_twophase test failure on kestrel |