pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: count(*) slow on large tables
Date: Mon, 06 Oct 2003 11:36:36 +0530
Message-ID: <3F81066C.90402@persistent.co.in> (raw)
In-Reply-To: <200310041819.h94IJkV07596@candle.pha.pa.us>
References: <200310041819.h94IJkV07596@candle.pha.pa.us>

Bruce Momjian wrote:
> OK, I beefed up the TODO:
> 
> 	* Use a fixed row count and a +/- count with MVCC visibility rules
> 	  to allow fast COUNT(*) queries with no WHERE clause(?)
> 
> I can always give the details if someone asks.  It doesn't seem complex
> enough for a separate TODO.detail item.

May I propose alternate approach for this optimisation?

- Postgresql allows to maintain user defined variables in shared memory.
- These variables obey transactions but do not get written to disk at all.
- There should be a facility to detect whether such a variable is initialized or 
not.

How it will help? This is in addition to trigger proposal that came up earlier. 
With  triggers it's not possible to make values visible across backends unless 
trigger updates a table, which eventually leads to vacuum/dead tuples problem.

1. User creates a trigger to check updates/inserts for certain conditions.
2. It updates the count as and when required.
3. If the trigger detects the count is not initialized, it would issue the same 
query first time. There is no avoiding this issue.

Besides providing facility of resident variables could be used imaginatively as 
well.

Does this make sense? IMO this is more generalised approach over all.

Just a thought.

  Shridhar






view thread (30+ messages)  latest in thread

Message-ID: <3F81066C.90402@persistent.co.in>
Permalink:  ../3F81066C.90402@persistent.co.in/
Also on:    postgresql.org/message-id/3F81066C.90402@persistent.co.in

 · 

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-performance@postgresql.org
  Cc: shridhar_daithankar@persistent.co.in
  Subject: Re: count(*) slow on large tables
  In-Reply-To: <3F81066C.90402@persistent.co.in>

* 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