"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > This highlights another problem with our plpgsql function caching.
> >
> > It's a little disturbing to think that any change in SEARCH_PATH might
> > force us to discard all cached plans
Gaetano Mendola wrote:
> "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > Tom Lane wrote:
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > > This highlights another problem with our plpgsql function caching.
> > >
> > > It's a little disturbing to think that any change in SEARCH_PATH might
> > >
Thanks. If I had only read the manual before posting. I solved it by
using 'execute' instead of 'select into' since the search_path is not
static in my system.
Gene
On Saturday, September 6, 2003, at 04:21 PM, Bruce Momjian wrote:
I think the problem is that the first time the function is c
Please help with a mac osx installation... I had
installed 7.3.4 on osx 10.2.6 some months ago. it was
a painless installation. I responded to someone on the
apple help list about installing. this person was
having a problem with the make stage. I didn't think
to retry making on my system.
I did.
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> any ideas... i believe the problem lies with the
> december 2002 update to the developers tools.
There is some recent traffic in our archives suggesting that Apple's
gcc 3.3 is busted. I have not been able to check this out because
my Powerbook is i
