Re: More tablescanning fun

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: jim(at)nasby(dot)net
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: More tablescanning fun
Date: 2003-04-27 06:50:51
Message-ID: 1051426250.1860.1.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jim C. Nasby kirjutas R, 25.04.2003 kell 19:56:
> I'm not familiar enough with pgsql's guts to know how big an impact
> updates across pages are, or if they even happen often at all. If you're
> not maintaining a clustered table, couldn't all updates just occur
> in-place?

In postgres _no_ updates happen in-place. The MVCC concurrency works by
always inserting a new tuple on update .

-----------
Hannu

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jeremy Andrus 2003-04-28 02:30:23 pgsql BLOB issues
Previous Message Tom Lane 2003-04-26 18:40:08 Re: Automatic analyze on select into