On Fri, Jun 25, 2004 at 06:35:08PM -0400, Sean McCune wrote:
> I'm not familiar with dbexperts version, but I think that's a native
> Win32 version, which shoots down cygwin as the culprit and starts
> pointing the finger at Windows. That figures.
Actually, AFAIR it _is_ a Cygwin version, relabel
I'm not familiar with dbexperts version, but I think that's a native
Win32 version, which shoots down cygwin as the culprit and starts
pointing the finger at Windows. That figures.
On Fri, 2004-06-25 at 06:39, Richard Huxton wrote:
> Sean McCune wrote:
> > OK, I'll look at it from the cygwin en
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:order by ignoring whitespaces on collate pt_BR
Most non-C locales are designed to do that. This isn't a bug.
regards, tom lane
---(end of broadcast)--
The following bug has been logged online:
Bug reference: 1183
Logged by: Everton Luis Berz
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux Slackware 9.1
Description:order by ignoring whitespaces on collate pt_BR
Details:
The ord
Sean McCune wrote:
OK, I'll look at it from the cygwin end. Its interesting that
restarting postgres clears it. Although, I guess this could be a
problem in the cygwin DLL. Thanks for the very quick response!
Just for the record, I had a client report the same thing a couple of
days ago with
Hi, i noticed a failure when i pg_dump/reload a database with tsearch2.sql
installed.
I get ERRORS of the type:
dynacom=# SELECT lexize('en_stem','foo bar');
ERROR: cache lookup failed for function 4652394
dynacom=# SELECT lexize('en_stem','foo bar');
ERROR: cache lookup failed for function 4
