Re: Tightening behaviour for non-immutable behaviour in immutable functions - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Tightening behaviour for non-immutable behaviour in immutable functions
Date
Msg-id 20221002010555.oytonheysherams6@awork3.anarazel.de
Whole thread Raw
In response to Re: Tightening behaviour for non-immutable behaviour in immutable functions  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
Hi,

On 2022-06-16 12:04:12 -0400, Greg Stark wrote:
> Of course this patch is still very WIP. Only one or the other function
> makes sense to keep. And I'm not opposed to having a GUC to
> enable/disable the enforcement or warnings. And the code itself needs
> to be cleaned up with parts of it moving to guc.c and/or namespace.c.

This currently obviously doesn't pass tests - are you planning to work on this
further?  As is I'm not really clear what the CF entry is for. Given the
current state it doesn't look like it's actually looking for review?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: TAP output format in pg_regress
Next
From: Andres Freund
Date:
Subject: Re: Eliminating SPI from RI triggers - take 2