From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Christopher Travers <einhverfr(at)hotmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG: PLPGSQL function causes PgSQL process to die when |
Date: | 2003-10-23 14:32:40 |
Message-ID: | 20031023073219.E13271@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, 23 Oct 2003, Christopher Travers wrote:
> Hi all;
>
> I have two tables which have different security considerations wrapped into
> a view. Inserting into the view is done using a simple rule which inserts
> into both tables (tables have a 1:1 relationship and reflect the
> user-defined and admin-defined portions of a user profile). From psql,
> inserts into the table work as expected. However from a PLPGSQL function,
> any attempt to insert into the table causes the following error:
>
> FATAL: SPI: improper call to spi_dest_setup
>
> The query is a simple insert and the rule merely splits it into two inserts.
>
> The workaround is simply to insert into both tables in the view
> independently within the plpgsql function. But this seems like odd behavior
> that should not be occurring.
Can you give version information and a standalone example?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-10-23 14:49:35 | Re: BUG: PLPGSQL function causes PgSQL process to die when inserting into a view |
Previous Message | Christopher Travers | 2003-10-23 14:15:53 | BUG: PLPGSQL function causes PgSQL process to die when inserting into a view |