On Tue, May 3, 2022 at 5:16 PM Peter Smith <smithpb2...@gmail.com> wrote: > ...
> Avoiding unexpected differences like this is why I suggested the > option should have to be explicitly enabled instead of being on by > default as it is in the current patch. See my review comment #14 [1]. > It means the user won't have to change their existing code as a > workaround. > > ------ > [1] > https://www.postgresql.org/message-id/CAHut%2BPuqYP5eD5wcSCtk%3Da6KuMjat2UCzqyGoE7sieCaBsVskQ%40mail.gmail.com > Sorry I was wrong above. It seems this behaviour was already changed in the latest patch v5 so now the option value 'on' means what it always did. Thanks! ------ Kind Regards, Peter Smith. Fujitsu Australia
