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

Re: Optimize date query for large child tables: GiST or GIN?

From: Yeb Havinga <yebhavinga(at)gmail(dot)com>
To: David Jarvis <thangalin(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thombrown(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Optimize date query for large child tables: GiST or GIN?
Date: 2010-05-21 08:45:36
Message-ID: 4BF64830.4080902@gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
There is a thing that might lead to confusion in the previous post:
> create or replace function yearmod(int) RETURNS int
> as 'select (($1 >> 2) %32);'
> language sql
> immutable
> strict;
is equivalent with

create or replace function yearmod(int) RETURNS int
as 'select (($1 / 4) %32);'
language sql
immutable
strict;

and that is the function that was used with all the other output (it can 
be seen inlined in the explain output). I did not catch this until after 
the post.

regards,
Yeb Havinga



In response to

Responses

pgsql-performance by date

Next:From: venu madhavDate: 2010-05-21 09:38:43
Subject: Autovacuum in postgres.
Previous:From: Yeb HavingaDate: 2010-05-21 08:38:43
Subject: Re: Optimize date query for large child tables: GiST or GIN?

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