Yes it is most likely locale,
if you have core,
try to use on Solaris
pstack you_core_file, should be "pretty distinct" back trace
-----Original Message-----
From: Luis Magaña [mailto:joe666@gnovus.com]
Sent: Wednesday, July 16, 2003 11:06 AM
To: Andrew Sullivan
Cc: Postgresql General Mail List
Subject: Re: [GENERAL] ODBC query problem
I've moved the database to a third location in the same disk using
pg_dumpall, the new location works with no errors, the initdb was made
without localization.
The production db was inited with es_MX locale, may that has something
to do with the problem ?.
On Wed, 2003-07-16 at 12:40, Andrew Sullivan wrote:
> On Wed, Jul 16, 2003 at 12:36:34PM -0500, Luis Maga?a wrote:
> > I've already moved database to a diferent partition nad got the same
> > results, I wonder, if it is a hardware problem, why can I access
both
> > tables individually with no problem at all ?.
>
> Doesn't sound like hardware, then. I think you really do need a
> backtrace. gdb works fine in 32 bit, but you'll need the debugging
> symbols in place. Also, what version of Postgres and which compiler?
>
> A
--
Luis Magaña.
Gnovus Networks & Software.
www.gnovus.com
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match