Skip site navigation (1) Skip section navigation (2)

Re: Materializing a sequential scan

From: "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Materializing a sequential scan
Date: 2005-10-27 00:13:48
Message-ID: 20051027001348.GA7756@uio.no (view raw or flat)
Thread:
Lists: pgsql-performance
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/

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2005-10-27 00:51:03
Subject: Re: Materializing a sequential scan
Previous:From: Tom LaneDate: 2005-10-26 23:53:02
Subject: Re: Materializing a sequential scan

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group