From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: Materializing a sequential scan
Date: Thu, 27 Oct 2005 02:13:48 +0200
Message-ID: <20051027001348.GA7756@uio.no> (raw)
In-Reply-To: <12708.1130370782@sss.pgh.pa.us>
References: <20051019174544.GA32303@samfundet.no>
<20051026213730.GA2295@uio.no>
<12333.1130367975@sss.pgh.pa.us>
<20051026232219.GA6390@uio.no>
<12708.1130370782@sss.pgh.pa.us>
On Wed, Oct 26, 2005 at 07:53:02PM -0400, Tom Lane wrote:
> I don't think you're getting a correct reading for optup, but OID
> 2373 is timestamp = date:
>
> [...]
>
> My recollection is that there was no such operator in 7.4; probably in
> 7.4 the IN ended up using timestamp = timestamp which is hashable.
You are quite correct, there is no such operator (whether by oid or by
description) in my 7.4 installation.
> What's not clear though is why you're getting that operator --- aren't
> both sides of the IN of type "date"?
Aha!
Figured out the "start" column wasn't the problem after all. The problem was
the "stopp" column, which was timestamp on one side and date on the other...
So, it can be fixed for this instance, but this feels a bit like the pre-8.0
joins on differing data types -- is there any way to fix it? :-)
/* QSteinar */
--
Homepage: http://www.sesse.net/
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sgunderson@bigfoot.com
Subject: Re: Materializing a sequential scan
In-Reply-To: <20051027001348.GA7756@uio.no>
* 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