Re: sepgsql contrib module
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: KaiGai Kohei <kaigai@ak.jp.nec.com>, KaiGai Kohei <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-01-21T15:46:53Z
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
Robert Haas <robertmhaas@gmail.com> writes: > On Fri, Jan 21, 2011 at 9:55 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> ALTER FUNCTION is supposed to cause plan invalidation in such a case. >> Not sure if GRANT plays nice with that though. > And in the case of SE-Linux, this could get changed from outside the > database. Not sure how to handle that. I guess we could just never > inline anything, but that might be an overreaction. I think SELinux is just out of luck in that case. If it didn't refuse execution permission at the time we checked before inlining (which we do), it doesn't get to change its mind later. regards, tom lane