Views + Rules + Triggers + 7.3.2 = Upgrade Problems (was: Re: REWRITE_INVOKE_MAX and "query may contain cycles" )

From: Eric B(dot)Ridge <ebr(at)tcdi(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: ebr(at)tcdi(dot)com
Subject: Views + Rules + Triggers + 7.3.2 = Upgrade Problems (was: Re: REWRITE_INVOKE_MAX and "query may contain cycles" )
Date: 2003-02-21 20:09:45
Message-ID: 6BC2A7EF-45D8-11D7-9F63-0003937E3354@tcdi.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Friday, February 21, 2003, at 11:11 AM, Eric B.Ridge wrote:
> Thanks for this information. Y'all rock. These two things are enough
> to convince me to upgrade to 7.3 immediately.

So after upgrading from 7.2.3 to 7.3.2, I've got some interesting
problems.

The backend simply saysr:
FATAL: SPI: improper call to spi_dest_setup

And psql says basically the same thing:
FATAL: SPI: improper call to spi_dest_setup
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.

And the jdbc drivers just go nuts. But since I can duplicate this in
psql, I'm sure it's not a JDBC specific issue.

Rather than try to explain what is happening, please checkout the
attached testcase. However, I believe I've narrowed it down to (at
least) an after-insert trigger (on a table w/ a view/rule facade) that
then tries to do an insert into a different (and mostly unrelated) view.

The expected results (as are produced by 7.2.3 are attached) as well.

If more information is necessary, please let me know.

thanks in advance!

eric

Attachment Content-Type Size
expected_results.txt text/plain 324 bytes
testcase.txt text/plain 2.5 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dmitry Tkach 2003-02-21 20:17:36 Re: A problem with sequences...
Previous Message Ruben 2003-02-21 20:09:11 How to update rows from a cursor in PostgreSQL