Re: CREATE OR REPLACE MATERIALIZED VIEW - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: CREATE OR REPLACE MATERIALIZED VIEW
Date
Msg-id 366B2727-F134-4FB6-93B9-BCB7DFF6F208@yesql.se
Whole thread Raw
In response to Re: CREATE OR REPLACE MATERIALIZED VIEW  (Erik Wienhold <ewie@ewie.name>)
List pgsql-hackers
> On 2 Jul 2024, at 15:58, Erik Wienhold <ewie@ewie.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




pgsql-hackers by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: CREATE OR REPLACE MATERIALIZED VIEW
Next
From: Tom Lane
Date:
Subject: Re: Underscore in positional parameters?