Re: BUG #2372: dblink_exec doesn't return. NEVER! - Mailing list pgsql-bugs

From Jim Nasby
Subject Re: BUG #2372: dblink_exec doesn't return. NEVER!
Date
Msg-id DA0752C5-E3EC-42F2-89B9-041D29C07FF3@pervasive.com
Whole thread Raw
In response to Re: BUG #2372: dblink_exec doesn't return. NEVER!  ("William Leite Araújo" <william.bh@gmail.com>)
List pgsql-bugs
On Apr 5, 2006, at 7:28 AM, William Leite Ara=FAjo wrote:

> On 4/3/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> (...)
> You need to read up on SECURITY DEFINER functions.
>
>                         regards, tom lane
>
>
>   Ok, I'll do this way, but still don't understand why it doesn't=20=20
> returns.
>    I'm doing things simillar to this to create users automatically,=20=20
> and works fine...

As Tom mentioned, it's probably an issue of waiting on a lock that it=20=20
can't acquire. Just because it worked for creating users doesn't mean=20=20
it's a good idea. It's certainly less efficient than a SECURITY=20=20
DEFINER function, for starters...
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-bugs by date:

Previous
From: Jim Nasby
Date:
Subject: Re: PostgreSQL 8.1.3.6044 crashes randomly.
Next
From: Tom Lane
Date:
Subject: Re: BUG #2379: Duplicate pkeys in table