Re: [REVIEW] prepare plans of embedded sql on function start - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: [REVIEW] prepare plans of embedded sql on function start
Date
Msg-id CABRT9RBOsSR=32OFFujauZVTW18+UpBzRcz8YzYX+yHpHeoy1Q@mail.gmail.com
Whole thread Raw
In response to Re: [REVIEW] prepare plans of embedded sql on function start  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [REVIEW] prepare plans of embedded sql on function start
List pgsql-hackers
On Sun, Sep 11, 2011 at 01:21, Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Marti Raudsepp
Date:
Subject: [WIP] Caching constant stable expressions per execution
Next
From: Tom Lane
Date:
Subject: Re: [WIP] Caching constant stable expressions per execution