| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Improving inferred query column names |
| Date: | 2023-02-22 13:23:51 |
| Message-ID: | 85015751-7a0a-9bbf-a6b6-aae68863e197@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-02-22 13:35:34 | Re: Seek for helper documents to implement WAL with an FDW |
| Previous Message | Matthias van de Meent | 2023-02-22 13:14:02 | Re: Ignoring BRIN for HOT updates (was: -udpates seems broken) |