> Very much obliged! I'll be watching the mailing lists, but if anyone
> does solve it, and happens to remember, please drop me a note.
> If there's anything more I can do to help, let me know. Thanks!
I am sure I can get it fixed by 6.6.
> >I am no closer to fixing this, but have added it to our TODO list.
> >> Thanks -- I did a similar change, which had similar results.
> >> I'm afraid I can't be of any help on the question of how
> >> BSDI handles shared libraries. I don't currently have a support
> >> contract with them, so I don't have a graceful "in" to ask them.
> >> I would say you have now duplicated the problem I was asking about,
> >> and if someone can solve it, I'll be a very happy fella.
> >> >Not sure what is causing that. My guess is that the there is still a
> >> >problem with the parser internals referenced by plpgsql on bsdi. Please
> >> >try my patch, and let me know if it improves things.
> >> >
> >> >Jan, any ideas?
> >> >
> > Bruce Momjian | http://www.op.net/~candle
> > maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> > + If your life is a hard drive, | 830 Blythe Avenue
> > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-ports by date
|Next:||From: Chris Parker||Date: 1999-09-28 14:01:21|
|Subject: pgsql new installation|
|Previous:||From: Nat Howard||Date: 1999-09-28 04:42:27|
|Subject: Re: [PORTS] plpgsql & bsdi 4.0 |