Re: [BUG] SECURITY DEFINER on call handler makes daemon crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, PostgreSQL-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUG] SECURITY DEFINER on call handler makes daemon crash
Date: 2010-03-20 00:11:13
Message-ID: 25179.1269043873@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Mar 19, 2010 at 8:18 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> writes:
>>> When we assign "SECURITY DEFINER" attribute on plpgsql_call_handler(),
>>> it makes server process crashed.
>>
>> So don't do that. Whatever possessed you to think that's a sensible
>> idea anyway?

> It might not be sensible, but the whole server going down as a result
> doesn't seem very sensible either.

[ shrug... ] If you would like to start enumerating the ways in which
you can crash the server with erroneous pg_proc entries for C functions,
go for it. It'll keep you out of trouble for a very long time.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-03-20 02:17:41 Re: [BUG] SECURITY DEFINER on call handler makes daemon crash
Previous Message Robert Haas 2010-03-19 23:12:40 Re: C libpq frontend library fetchsize