On 2019-03-11 09:31, Michael Paquier wrote: > On Mon, Mar 11, 2019 at 08:23:39AM +0100, Peter Eisentraut wrote: >> Attached patch fixes a couple of cases of that. Most instances were >> already correct. > > It seems to me that you should look at that: > https://www.postgresql.org/message-id/20190308055911.gg4...@paquier.xyz > They treat about the same subject, and a patch has been sent for this > CF.
I'm aware of that patch and have been looking at it. But it's not directly related to this issue. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
