Re: Improving inferred query column names - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Improving inferred query column names
Date
Msg-id 85015751-7a0a-9bbf-a6b6-aae68863e197@enterprisedb.com
Whole thread Raw
In response to Re: Improving inferred query column names  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On 20.02.23 16:17, David G. Johnston wrote:
>     I think we should just do it and not care about what breaks.  There has
>     never been any guarantee about these.
> 
> 
> I'm going to toss a -1 into the ring but if this does go through a 
> strong request that it be disabled via a GUC.  The ugliness of that 
> option is why we shouldn't do this.
> 
> Defacto reality is still a reality we are on the hook for.
> 
> I too find the legacy design choice to be annoying but not so much that 
> changing it seems like a good idea.

Well, a small backward compatibility GUC might not be too cumbersome.




pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)
Next
From: Peter Eisentraut
Date:
Subject: Re: Seek for helper documents to implement WAL with an FDW