Re: CREATE OR REPLACE MATERIALIZED VIEW

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Erik Wienhold <ewie(at)ewie(dot)name>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Aleksander Alekseev <aleksander(at)timescale(dot)com>
Subject: Re: CREATE OR REPLACE MATERIALIZED VIEW
Date: 2024-07-02 14:01:45
Message-ID: 366B2727-F134-4FB6-93B9-BCB7DFF6F208@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Jul 2024, at 15:58, Erik Wienhold <ewie(at)ewie(dot)name> wrote:
> On 2024-07-02 14:27 +0200, Daniel Gustafsson wrote:
>> Considering the runway we typically give for deprecations, that seems like a
>> fairly short timeframe for a SQL level command which isn't unlikely to exist
>> in application code.
>
> Is there some general agreed upon timeframe, or is decided on a
> case-by-case basis? I can imagine waiting at least until the last
> release without the deprecation reaches EOL. That would be 5 years with
> the current versioning policy.

AFAIK it's all decided on a case-by-case basis depending on impact. There are
for example the removals you listed, and there are functions in libpq which
were deprecated in the postgres 6.x days which are still around to avoid
breaking ABI.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-07-02 14:14:48 Re: Underscore in positional parameters?
Previous Message Erik Wienhold 2024-07-02 13:58:06 Re: CREATE OR REPLACE MATERIALIZED VIEW