Re: SPI_ERROR_CONNECT - Mailing list pgsql-general

From Willem Buitendyk
Subject Re: SPI_ERROR_CONNECT
Date
Msg-id 47B143A9.6010300@pcfish.ca
Whole thread Raw
In response to Re: SPI_ERROR_CONNECT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

Tom Lane wrote:

 >That's a fairly bad workaround (assuming that the function is a
 > legitimate candidate to be IMMUTABLE) because it defeats potential
 > optimizations.
 >
 > What I'd suggest you do instead is rethink your apparently widespread
 > habit of whacking your view definitions around on-the-fly.  This would
 > never have worked at all before PG 8.3 (and as you can see we still have
 > some bugs left in supporting it in 8.3 :-().  Even when it does work,
 > there is a whole lot of frantic paddling going on just under the
 > surface.  We may sail serenely on like the swan, but not very speedily

Yep, already started reorganizing so that I don't have to hack away at
the views so much.  So far I've been
able to do without the functions that would only work with volatile.

cheers,

willem

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: SPI_ERROR_CONNECT
Next
From: Ken Johanson
Date:
Subject: Re: SELECT CAST(123 AS char) -> 1