Ranier Vilela <ranier...@gmail.com> writes:
> It seems that 1ec7679f1b67e84be688a311dce234eeaa1d5de8 caused the problem.

Indeed.  Fix pushed.

                        regards, tom lane


Reply via email to