Re: pgsql: Database-level collation version tracking - Mailing list pgsql-committers

From Peter Eisentraut
Subject Re: pgsql: Database-level collation version tracking
Date
Msg-id 825db713-7298-db4c-7189-1572a4f29888@eisentraut.org
Whole thread Raw
In response to Re: pgsql: Database-level collation version tracking  (Michael Paquier <michael@paquier.xyz>)
List pgsql-committers
On 14.02.22 09:18, Michael Paquier wrote:
> calliphoridae does not like this one:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2022-02-14%2007%3A41%3A13
> 
>   SELECT current_database() AS datname \\gset
>   ALTER DATABASE :"datname" REFRESH COLLATION VERSION;
> -NOTICE:  version has not changed
> +ERROR:  unrecognized node type: 291
> 
> Worth noting that it uses -DDCOPY_PARSE_PLAN_TREES and
> -DRAW_EXPRESSION_COVERAGE_TEST, so you may have missed a piece in this
> area.

Fun fact: You'd think that just copying "-DDCOPY_PARSE_PLAN_TREES 
-DRAW_EXPRESSION_COVERAGE_TEST" into, say, COPT, would help debug this, 
but that only works if the originals are spelled correctly. ;-)



pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Suppress integer-overflow compiler warning for inconsistent sun_
Next
From: Heikki Linnakangas
Date:
Subject: Re: pgsql: Add test case for an archive recovery corner case.