| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Introduce a new view for checkpointer related stats |
| Date: | 2022-11-29 22:29:12 |
| Message-ID: | CAM-w4HPkz_fmhF8Pttp=TRk2XS+P5LhRbBdeA092RO88DZrt0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 28 Nov 2022 at 13:00, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Tue, Nov 22, 2022 at 3:53 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I vote to just remove them. I think that most people won't update
> their queries until they are forced to do so. I don't think it
> matters very much when we force them to do that.
I would tend to agree.
If we wanted to have a deprecation period I think the smooth way to do
it would be to introduce two new functions/views with the new split.
Then mark the entire old view as deprecated. That way there isn't a
mix of new and old columns in the same view/function.
I don't think it's really necessary to do that here but there'll
probably be instances where it would be worth doing.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2022-11-29 22:51:49 | Re: Patch: Global Unique Index |
| Previous Message | Thomas Munro | 2022-11-29 21:52:46 | Re: Collation version tracking for macOS |