On Apr 5, 2006, at 7:28 AM, William Leite Araújo wrote:
On 4/3/06, Tom Lane <[EMAIL PROTECTED]> 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
returns.
I'm doing t
On 4/3/06, Tom Lane <[EMAIL PROTECTED]> 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 returns. I'm doing things simillar to this to create users automatically, and works fin
"=?ISO-8859-1?Q?William_Leite_Ara=FAjo?=" <[EMAIL PROTECTED]> writes:
> I need this to give a credit from canceled billets.
> But anyone instead of roots can insert on this table.
> If it's done by a function, only roots must run it. So, the trigger
> will fail because is runned a no
I need this to give a credit from canceled billets. But anyone instead of roots can insert on this table. If it's done by a function, only roots must run it. So, the trigger will fail because is runned a no "su"...
On 4/3/06, Stephen Frost <[EMAIL PROTECTED]> wrote:
* Tom Lane ([EMAIL
* Tom Lane ([EMAIL PROTECTED]) wrote:
> dblink connections to your own database are very seldom a good idea;
> there is always a better, more efficient, less deadlock-prone way
> to do it. In this case I'd venture that you want to use a SECURITY
> DEFINER function, and not dblink at all.
The one
"William Leite Araújo" <[EMAIL PROTECTED]> writes:
> A trigger start a dblink_exec local connection to insert on a table "A" as
> SuperUser. Table "A" fires insert trigger that, by LOG messages, ends, but
> the function never return to initial trigger.
Perhaps the other transaction is blocked on
The following bug has been logged online:
Bug reference: 2372
Logged by: William Leite Araújo
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.7
Operating system: i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5
(Debian 1:3.3.5-13)
Description:dblink_exec d
