pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ian Cass <ian.cass@mblox.com>
To: Dima Tkach <dmitry@openratings.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Date indexing
Date: Tue, 23 Apr 2002 15:07:49 +0100
Message-ID: <003001c1ead0$41169260$6602a8c0@salamander> (raw)
References: <005501c1eaaa$46eb2500$6602a8c0@salamander>
	<3CC559FF.1030209@openratings.com>

> This won't be able to make much use of the compound index, because you
> are not searching for exact match on the first column, and the other
> columns are not in your criteria at all ... Thus your index is only as
> good as being just on the timestamp alone.

This makes sense. I'll change the order of my indexing.

> 10 minutes still sounds pretty excessive though, even for a seq. scan
> on a 5000 rows table. Have you vacuum'ed it lately?
> Try running 'vacuum full' on that table, it might help a lot, if you
> were ding lots of updates to it.


No, the actual table contains more like 10mill lines, however, the dataset
I'd be referencing if the index were working as I intended would be a mere
5k rows.

Thanks for your help. I'll try this later today.

--
Ian Cass




view thread (5+ messages)

Message-ID: <003001c1ead0$41169260$6602a8c0@salamander>
Permalink:  ../003001c1ead0$41169260$6602a8c0@salamander/
Also on:    postgresql.org/message-id/003001c1ead0$41169260$6602a8c0@salamander

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: ian.cass@mblox.com, dmitry@openratings.com
  Subject: Re: Date indexing
  In-Reply-To: <003001c1ead0$41169260$6602a8c0@salamander>

* 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