Re: sepgsql contrib module

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: KaiGai Kohei <kaigai@ak.jp.nec.com>

Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>

Date: 2011-01-21T14:05:57Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pgindent run for 9.0, second run
- 239d769e7e05 9.0.0 cited

2011/1/21 KaiGai Kohei <kaigai@ak.jp.nec.com>:
> - Add checks to avoid inlining function without db_procedure:{execute}
>  permission. Sorry, process:{transition} shall be checked in other place.

Hrm.  What happens if permissions change between plan time and execution time?

For that matter, I wonder what happens with regular function
permissions.  If the plan inlines the function and then somebody goes
and changes the permission on the function and makes it SECURITY
DEFINER, what happens?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company