Re: [REVIEW] prepare plans of embedded sql on function start

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andy Colson <andy(at)squeakycode(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, pavel(dot)stehule(at)gmail(dot)com
Subject: Re: [REVIEW] prepare plans of embedded sql on function start
Date: 2011-09-10 22:43:50
Message-ID: CABRT9RBOsSR=32OFFujauZVTW18+UpBzRcz8YzYX+yHpHeoy1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 11, 2011 at 01:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm not that happy with overloading the ANALYZE keyword to mean this
> But we could certainly use some other name --- I'm
> inclined to suggest CHECK:
>        CHECK FUNCTION function_name(arglist);

Just a thought: pg_check_function(oid)?

> People would want some sort of wild card capability; at the very least
> "check all plpgsql functions owned by me".

SELECT pg_check_function(p.oid) FROM pg_proc p
JOIN pg_user ON (usesysid=proowner) WHERE usename=current_user;

Regards,
Marti

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-09-10 22:51:31 Re: [WIP] Caching constant stable expressions per execution
Previous Message Marti Raudsepp 2011-09-10 22:27:17 [WIP] Caching constant stable expressions per execution