Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation
От | Masahiko Sawada |
---|---|
Тема | Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation |
Дата | |
Msg-id | CAD21AoA7ic0YR_WLOkGgnAG1=+WdGGPDcNWGTmsMm8rsTvG3tQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation
|
Список | pgsql-hackers |
On Tue, Apr 30, 2024 at 12:37 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Masahiko Sawada <sawada.mshk@gmail.com> writes: > > On Tue, Apr 23, 2024 at 11:57 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> Reject as not a bug. Discourage people from thinking that physical > >> replication will work across architectures. > > > While cross-arch physical replication is not supported, I think having > > architecture dependent differences is not good and It's legitimate to > > fix it. FYI the 'char' data type comparison is done as though char is > > unsigned. I've attached a small patch to fix it. What do you think? > > I think this will break existing indexes that are working fine. > Yeah, it would have been better to avoid the difference, but > it's too late now. True. So it will be a PG18 item. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: