hought with the OLTP applications in
mind, then this is not at all a suitable option. This will only benefit the
people with Data Warehouses.
Expecting some more replies
Thanks,
Gokul.
On 9/20/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> "Gokulakannan Somsundaram" <[EM
The obvious advantages are
a) Avoidance of one read lock per page
b) One Big write lock instead of multiple write locks.
But as you said, i will do some initial profiling and get back.
Thanks,
Gokul.
On 9/20/07, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
>
> Gokulakannan Somsu
Hi,
The Current architecture of Updates in PostgreSQL is
1) Make a select query out of update. It involves a READ lock/BUFFER_SHARE
2) Get the tupleid
3) Goto the buffer containing the tupleid, make a BUFFER_EXCLUSIVE lock on
it
4) update it
5) Repeat the above process for subsequent rows
I pro
