pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Martin Foster <martin@ethereal-realms.org>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Efficiency of timestamps
Date: Tue, 08 Jul 2003 22:23:38 -0600
Message-ID: <3F0B98CA.90800@ethereal-realms.org> (raw)
In-Reply-To: <20030708192541.D5781-100000@megazone23.bigpanda.com>
References: <20030708192541.D5781-100000@megazone23.bigpanda.com>

Stephan Szabo wrote:
> 
> 
> The row estimate is high. How many rows meet the various conditions and
> some of the combinations? And how many rows does it estimate if you do a
> simpler query on those with explain?
> 
> I still think some variety of multi-column index to make the above index
> conditions would help, but you'd probably need to play with which ones
> help, and with the cost cut for the limit, I don't know if it'd actually
> get a better plan, but it may be worth trying a bunch and seeing which
> ones are useful and then dropping the rest.
> 
> 

At any given point in time you would not expect to see much more then 30 
posts applying for a time based search.    That is primarily a result of 
having more then one room for which posts are attached to, and then some 
posts exist just to show people are there et cetera.

Simpler queries seem to do quiet well.   That view makes use of the same 
table and seems to have no performance impact from doing as such, and 
the position based search is considerably faster.

I can show EXPLAIN ANALYSE for all of those if you wish.

	Martin Foster
	Creator/Designer Ethereal Realms
	martin@ethereal-realms.org





view thread (7+ messages)  latest in thread

Message-ID: <3F0B98CA.90800@ethereal-realms.org>
Permalink:  ../3F0B98CA.90800@ethereal-realms.org/
Also on:    postgresql.org/message-id/3F0B98CA.90800@ethereal-realms.org

 · 

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-performance@postgresql.org
  Cc: martin@ethereal-realms.org, sszabo@megazone23.bigpanda.com
  Subject: Re: Efficiency of timestamps
  In-Reply-To: <3F0B98CA.90800@ethereal-realms.org>
  References: <20030708192541.D5781-100000@megazone23.bigpanda.com> <3F0B98CA.90800@ethereal-realms.org>

* 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