Shelby Cain <alyandon(at)yahoo(dot)com> writes:
> I had already removed proprietary data to try and
> whittle down the number of columns I needed to
> demonstrate the weirdness so I can host a dump of the
> table. However, before I take that step I should
> mention that this is the native Windows port so if
> that changes anything let me know.
Well, if I can't reproduce the misbehavior on a Unix machine then
there'll be reason to suspect a platform-specific bug ... but it's
still a bug.
It'll be important to know the exact datatypes of the columns,
as well as the database locale and encoding you are using.
regards, tom lane
In response to
pgsql-hackers-win32 by date
|Next:||From: Tom Lane||Date: 2005-05-01 17:03:55|
|Subject: Re: [GENERAL] Increasing statistics results in worse estimates |
|Previous:||From: Shelby Cain||Date: 2005-04-29 16:54:11|
|Subject: Re: Increasing statistics results in worse estimates |
pgsql-general by date
|Next:||From: Mike Nolan||Date: 2005-04-29 17:32:26|
|Subject: Tuning queries inside a function|
|Previous:||From: Tom Lane||Date: 2005-04-29 17:23:53|
|Subject: Re: Composite types as columns used in production? |