I've found another plperl bug in the most recent CVS sources (see
end of message for file versions). Sorry if this is a known issue
but I don't remember seeing it.
If spi_exec_query() fails in a plperl function, subsequent calls
to plperl or plperlu functions that hadn't been previously loaded
wi
> [ shrug... ] Works fine for me in unicode, too.
never mind me,. I broke it.
seems my assumption that UCS2 == UTF16 was way off
... john
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
PostgreSQL 8.0b4 as released.
select split_part('a b c d e f g h i j k l m n o p q r s t u v w x y
z',' ',1);
select split_part('a b c d e f g h i j k l m n o p q r s t u v w x y
z',' ',2);
select split_part('a b c d e f g h i j k l m n o p q r s t u v w x y
z',' ',3);
select split_part('a b c d e
> Works fine for me. What encoding/locale are you using?
unicode / c
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Fri, 19 Nov 2004, Tom Lane wrote:
This causes PostgreSQL not to start after the upgrade. It needs to be fixed
to:
# PGVERSION is:
PGVERSION=7.3
Devrim fixed that several days ago, I thought.
I've fixed for some distros, but could not fix for FC1
