@feld @pea I received same error, but I can resolve to upgrade PostgreSQL version.
I got this error at PostgreSQL 10.9, but it is resolved at PostgreSQL 11.x.