| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: remove bits* types |
| Date: | 2026-03-30 18:07:21 |
| Message-ID: | 2531742.1774894041@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> It's hard to get an exact count because the names are so common, but I'm
> seeing <10 packages on codesearch.debian.net that might be affected, and
> it's quite easy to fix (s/bits/uint/g). My experience is that we routinely
> "break" extensions like this in new major versions, too. So, I'm not
> convinced we need to do any kind of backward-compatibility work. In any
> case, we have a lot of time between now and GA, so if a bunch of angry
> extension authors come to my door with pitchforks, we can reconsider.
Agreed. As incompatible changes go, this is pretty darn minor
and easy to deal with.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-03-30 18:16:07 | Re: Add pg_stat_autovacuum_priority |
| Previous Message | Nathan Bossart | 2026-03-30 18:00:07 | Re: remove bits* types |