Re: BUG #18178: New Restriction on "ON SELECT" rules on tables

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: joshua(dot)uyehara(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
Date: 2023-11-02 09:44:15
Message-ID: C4A65972-B291-4D8D-BC32-364D2ABA935A@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 2 Nov 2023, at 00:25, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:

> In investigating the issue I did find what is likely the related release
> note for 16 "Remove the ability to create views manually with ON SELECT
> rules (Tom Lane)", but couldn't find any related discussion of the
> rationale, suggested workarounds, or whether anyone else has yet run into
> the same class of issues (possible given the recency of the release).

The discussion which led to this change can be found in this thread:

https://www.postgresql.org/message-id/flat/CALDaNm2yXz%2BzOtv7y5zBd5WKT8O0Ld3YxikuU3dcyCvxF7gypA%40mail.gmail.com

While it might not contain any workarounds, it might at least share insights
into the rationale for it.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-11-02 09:59:22 BUG #18179: Cluster History Error
Previous Message torikoshia 2023-11-02 03:24:50 Re: pg_rewind WAL segments deletion pitfall