From: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Doug McNaught <doug(at)mcnaught(dot)org> |
Subject: | Re: *sigh* |
Date: | 2003-11-30 02:21:23 |
Message-ID: | 3FC95423.5000204@bigfoot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Doug McNaught wrote:
> Randolf Richardson <rr(at)8x(dot)ca> writes:
>
>
>> What about adding a "total number of rows" value to the internal
>>header of each table which gets incremented/decremented after each row is
>>INSERT/DELETE has been committed. This way, a generic "count(*)" by itself
>>could simply return this value without any delay at all.
>
>
> Because different sessions have a (validly) different concept of what
> that number should be, due to MVCC.
The count(*) information can be revisioned too, am I wrong ? I'm able to
create a trigger that store the count(*) information in a special table,
why not implement the same in a way "builded in" ?
Regards
Gaetano Mendola
From | Date | Subject | |
---|---|---|---|
Next Message | Shane D | 2003-11-30 02:48:40 | Re: Was: Triggers, Stored Procedures, PHP |
Previous Message | Neil Conway | 2003-11-30 00:18:10 | Re: Materialized views proposal |