pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Steven M. Wheeler <swheeler@sabre.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] Re: pgsql-sql-digest V1 #225
Date: Mon, 24 May 1999 17:25:33 -0400 (EDT)
Message-ID: <199905242125.RAA26402@candle.pha.pa.us> (raw)
In-Reply-To: <3749A2DA.6529C21E@sabre.com>

> 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, Pennsylvania 19026



view thread (7+ messages)  latest in thread

Message-ID: <199905242125.RAA26402@candle.pha.pa.us>
Permalink:  ../199905242125.RAA26402@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199905242125.RAA26402@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: maillist@candle.pha.pa.us, swheeler@sabre.com, tgl@sss.pgh.pa.us, pgsql-sql@hub.org
  Subject: Re: [SQL] Re: pgsql-sql-digest V1 #225
  In-Reply-To: <199905242125.RAA26402@candle.pha.pa.us>
  References: <3749A2DA.6529C21E@sabre.com> <199905242125.RAA26402@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox