From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Doug Doole <ddoole(at)salesforce(dot)com> |
Subject: | Re: WIP: Faster Expression Processing v4 |
Date: | 2017-03-11 00:13:25 |
Message-ID: | 722ff25a-2a81-496a-791d-146329e4c8e7@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/10/17 14:24, Andres Freund wrote:
> What problem are you thinking of exactly, and what'd be the solution?
> I'd guess that people wouldn't like being unable to change columns in a
> table if some function returned the type.
Well, that's pretty much the problem.
For example:
create type t1 as (a int, b int);
create function f1() returns setof t1 language plpgsql
as $$ begin return query values (1, 2); end $$;
alter type t1 drop attribute b;
select * from f1(); -- fail
The dependency system should arguably guard against that. Yes, it would
make some things more cumbersome, but, well, it already does that.
>> Not necessarily in this patch, but I would like to keep the options
>> open.
>
> Yea, seems worth thinking about. I don't think the patch closes down
> options?
nope
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2017-03-11 00:15:15 | Re: make check-world output |
Previous Message | Peter Eisentraut | 2017-03-11 00:06:27 | Re: Need a builtin way to run all tests faster manner |