> On Apr 9, 2018, at 10:06 AM, Tom Lane <[email protected]> wrote: > > "Jonathan S. Katz" <[email protected]> writes: >> +1 based on running the above scenario on my 10.3 instance and >> receiving the same error. Is there a chance the fix could make it into >> 10.4 then? > > It's premature to discuss whether this could be back-patched when > we haven't got an acceptable patch yet.
Understood. Jonathan
