On Aug 29, 2013, at 2:48 PM, Andres Freund <and...@2ndquadrant.com> wrote:
>> You have yet to supply any arguments which support this position. > > I am not convinced that's enough of a reason, but the requirement to use > PERFORM for SELECTs that aren't stored anywhere actually has prevented > bugs for me. I am not convinced that's worth the cost since I also have > been annoyed by it several times, but it's not as crystal clear as you > paint it. So now we can revise Josh’s assertion to: “I have seen only tepid, unconvincing arguments which support this position.” I have thought that PERFORM was useful to mark queries that discard results in the past, but I think now that the mental load is higher, even if it can be fixed with CTEs, it’s more trouble than it’s worth. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers