Re: pgsql: Fix incorrect matching of subexpressions in outer-join plan node - Mailing list pgsql-committers

From Andres Freund
Subject Re: pgsql: Fix incorrect matching of subexpressions in outer-join plan node
Date
Msg-id 20150424211227.GA12723@awork2.anarazel.de
Whole thread Raw
In response to Re: pgsql: Fix incorrect matching of subexpressions in outer-join plan node  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 2015-04-24 13:30:49 -0400, Tom Lane wrote:
> [ catching up on email post-vacation ]

Welcome back Tom! Hope you had a nice and relaxing time.

> It's okay to store resulttype and retset
> because we disallow changing the output type (including set-ness) of a
> function; but we don't want to disallow changing strictness for
> instance.

I don't think we forbid changing the volatility. I'm pretty sure I've
changed that using CREATE OR REPLACE in the past.

Yep:
postgres[l]=# CREATE FUNCTION blarg() RETURNS int VOLATILE LANGUAGE SQL AS $$SELECT 1;$$;
CREATE FUNCTION
postgres[l]=# CREATE OR REPLACE FUNCTION blarg() RETURNS int STABLE LANGUAGE SQL AS $$SELECT 1;$$;
CREATE FUNCTION

Greetings,

Andres Freund


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix obsolete comment in set_rel_size().
Next
From: Tom Lane
Date:
Subject: pgsql: Fix up .gitignore and cleanup actions in some src/test/ subdirec