Re: [SQL] Re: pgsql-sql-digest V1 #225 - Mailing list pgsql-sql

From Bruce Momjian
Subject Re: [SQL] Re: pgsql-sql-digest V1 #225
Date
Msg-id 199905242125.RAA26402@candle.pha.pa.us
Whole thread Raw
In response to Re: [SQL] Re: pgsql-sql-digest V1 #225  ("Steven M. Wheeler" <swheeler@sabre.com>)
List pgsql-sql
> Tom,
> 
> I have a little more information.
> 
> Version of Postgres: 6.4.2
> 
> Regarding your request for a backtrace, I recompiled with debugging and
> profiling options on.  Subsequently I have attached the debugger and
> interrupted the backend a number of times.  I keep coming up in mcount() and
> a couple of hash functions.  BTW: I had let the query run for over 50+ hours
> without it returning a value.  The offending SQL: select count(*) from
> currnt;  Is there something more definitive you would like me to do?
> 
> Using the syntax you suggested, "statdate >= 'date' and statdate <= 'date'"
> works like a champ.  So does using "between" as suggested by another user.
> However, issuing "select count(*) form currnt where statdate = '03-01-1999';
> still returns an error telling me that I must use a cast since there is more
> than one possible function.

I hate to say this but 6.5 is just about to be released, and has major
hashjoin fixes that may fix this problem.  Can you try the most recent
snapshot on ftp.postgresql.org.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-sql by date:

Previous
From: "Steven M. Wheeler"
Date:
Subject: Fatal process interaction
Next
From: Mirek Budzanowski
Date:
Subject: index on int8 in PG 6.4.2