From: Tom Lane <tgl@sss.pgh.pa.us>
To: "johnlumby@hotmail.com" <johnlumby@hotmail.com>
cc: pgsql-general@lists.postgresql.org,
        Adrian Klaver <adrian.klaver@aklaver.com>,
        "David G. Johnston" <david.g.johnston@gmail.com>
Subject: Re: Rules and Command Status - update/insert/delete rule with series of commands in action
In-reply-to: <PH0PR10MB695991BDE3588B549CE6A4D7A3F32@PH0PR10MB6959.namprd10.prod.outlook.com>
References: <PH0PR10MB6959209E2B0F36BE765E9159A3F32@PH0PR10MB6959.namprd10.prod.outlook.com> <d9633950-7f00-49c2-9f74-3b2b1ae0fce0@aklaver.com> <PH0PR10MB695991BDE3588B549CE6A4D7A3F32@PH0PR10MB6959.namprd10.prod.outlook.com>
Comments: In-reply-to "johnlumby@hotmail.com" <johnlumby@hotmail.com>
	message dated "Thu, 30 May 2024 18:34:23 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <4350.1717119247.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Thu, 30 May 2024 18:34:07 -0700
Message-ID: <4351.1717119247@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/4351.1717119247%40sss.pgh.pa.us>
Precedence: bulk

"johnlumby@hotmail.com" <johnlumby@hotmail.com> writes:
> But I suppose that my next question,   given what you both say about the 
> RULE system being a dead-end,  is whether there is any likelihood of 
> supporting an INSTEAD OF trigger on a view at statement level?   Maybe 
> that stands more chance of going somewhere?

Perhaps, but I don't know of anyone working on it.

IIRC, the row-level-only restriction dates from before we had
implemented transition tables, so that at the time there was
nothing very meaningful that a statement-level trigger could do.
Maybe that problem has gone away, though I've not thought
about it very hard.

			regards, tom lane