Re: Proposal: pg_is_volatile function

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Farries <andrew(dot)farries(at)xata(dot)io>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: pg_is_volatile function
Date: 2025-02-20 18:21:59
Message-ID: CAFj8pRCou4mjXCHs4dRfq-45jL+PQk+74QSH=n2oVEQrXO6usw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

> What we have speculated about in the past is extending EXPLAIN
> so that it can be applied to ALTER TABLE and other complicated
> utility commands, and then for ALTER TABLE one bit of info it would
> give you is whether a table rewrite (or even a table scan) is
> required. Obviously, that's a major project, and so nobody's
> tackled it yet AFAIK.
>

I though same idea, using EXPLAIN for this purpose can be nice and intuitive

Regards

Pavel

>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Devulapalli, Raghuveer 2025-02-20 18:23:56 RE: Improve CRC32C performance on SSE4.2
Previous Message Tom Lane 2025-02-20 18:21:25 Re: Improvement of var_eq_non_const()