| From: | Jaime Casanova <systemguards(at)gmail(dot)com> | 
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> | 
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Alexander Scholz <alexander(dot)scholz1(at)freenet(dot)de>, pgsql general <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: Indices for select count(*)? | 
| Date: | 2005-12-22 16:30:31 | 
| Message-ID: | c2d9e70e0512220830w554f3563g71321806ac00b58c@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
>
> I wouldn't mind a "with visibility" switch for indexes that you could
> throw when creating them for this purpose.  But burdening all indexes
> with this overhead when most wouldn't need it is not, IMHO, a good idea.
>
that would add complexity to the index code for... just one case?
what about a set of functions instead...
one function to create all necesary triggers  to maintain a different
table with a count for the table, and one function that retrieves that
info
select start_counter_on_table('table_name');
select get_counter_on_table('table_name');
of course, this could be usefull just for the case of "select * from
table"... but that case is the whole problem...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-12-22 16:33:32 | Re: About Maximum number of columns | 
| Previous Message | Peter Eisentraut | 2005-12-22 16:16:16 | Re: Is CREATE TYPE an alias for CREATE DOMAIN? |