From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Mats Kindahl <mats(at)timescale(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, jakub(dot)wartak(at)enterprisedb(dot)com |
Subject: | Re: Use streaming read API in ANALYZE |
Date: | 2024-09-04 15:36:21 |
Message-ID: | CA+TgmobsSqwCzFFQqPcTtx8UKk5hwS8X2zGqVXfW+VdC0KPFOw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 4, 2024 at 6:38 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Thanks for the explanation. I think we should revert it. IMHO it was
> a nice clean example of a streaming transformation, but unfortunately
> it transformed an API that nobody liked in the first place, and broke
> some weird and wonderful workarounds. Let's try again in 18.
The problem I have with this is that we just released RC1. I suppose
if we have to make this change it's better to do it sooner than later,
but are we sure we want to whack this around this close to final
release?
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2024-09-04 15:37:24 | Re: scalability bottlenecks with (many) partitions (and more) |
Previous Message | David Rowley | 2024-09-04 15:34:31 | Re: Typos in the code and README |