| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fixing the btree_gist inet mess |
| Date: | 2025-12-18 11:31:39 |
| Message-ID: | 0c2a0b34-b0fa-454e-a488-dddca7ca2411@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18/12/2025 13:15, Heikki Linnakangas wrote:
> On 01/08/2025 21:17, Tom Lane wrote:
>> It's past time to move this problem along and try to get out of the
>> business of encouraging use of known-broken code. I propose that
>> for v19, we should flip the opcdefault status so that network_ops is
>> marked default and the btree_gist opclasses are not. This will be
>> enough to ensure that network_ops is used unless the user explicitly
>> specifies to do differently.
>
> +1
>
> Bunch of ideas and opinions below, but I'm fine with your plan as is too:
Sorry, I was confused by my emails and replied to this old email
ignoring the later discussion. But I think all I said is still valid,
and some of it was already mentioned.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-12-18 11:33:20 | Re: Logical Replication of sequences |
| Previous Message | Heikki Linnakangas | 2025-12-18 11:15:36 | Re: Fixing the btree_gist inet mess |