From: Hannu Krosing <hannu@tm.ee>
To: jim@nasby.net
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: More tablescanning fun
Date: 27 Apr 2003 09:50:51 +0300
Message-ID: <1051426250.1860.1.camel@fuji.krosing.net> (raw)
In-Reply-To: <20030425115613.E66185@flake.decibel.org>
References: <20030424183817.A66185@flake.decibel.org>
<3660.1051228710@sss.pgh.pa.us>
<20030424235924.B66185@flake.decibel.org>
<1051288086.1765.95.camel@fuji.krosing.net>
<20030425115613.E66185@flake.decibel.org>
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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: hannu@tm.ee, jim@nasby.net, tgl@sss.pgh.pa.us
Subject: Re: More tablescanning fun
In-Reply-To: <1051426250.1860.1.camel@fuji.krosing.net>
References: <20030424183817.A66185@flake.decibel.org> <3660.1051228710@sss.pgh.pa.us> <20030424235924.B66185@flake.decibel.org> <1051288086.1765.95.camel@fuji.krosing.net> <20030425115613.E66185@flake.decibel.org> <1051426250.1860.1.camel@fuji.krosing.net>
* 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