Re: Tightening behaviour for non-immutable behaviour in immutable functions
От
Andres Freund
Тема
Re: Tightening behaviour for non-immutable behaviour in immutable functions
Дата
Msg-id
20221002010555.oytonheysherams6@awork3.anarazel.de
Ответ на
Список
Дерево обсуждения
Tightening behaviour for non-immutable behaviour in immutable functions Greg Stark <stark@mit.edu>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Mark Dilger <mark.dilger@enterprisedb.com>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Greg Stark <stark@mit.edu>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Peter Geoghegan <pg@bowt.ie>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Greg Stark <stark@mit.edu>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Peter Geoghegan <pg@bowt.ie>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Michael Paquier <michael@paquier.xyz>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Greg Stark <stark@mit.edu>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Andres Freund <andres@anarazel.de>
Re: Tightening behaviour for non-immutable behaviour in immutable functions Greg Stark <stark@mit.edu>
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 по дате отправления