From: Rod Taylor <pg@rbt.ca>
To: Yves Vindevogel <yves.vindevogel@implements.be>
Cc: pgsql-performance@postgresql.org
Subject: Re: Updates on large tables are extremely slow
Date: Mon, 13 Jun 2005 12:53:19 -0400
Message-ID: <1118681599.723.105.camel@home> (raw)
In-Reply-To: <93fcaa35413e2059526ab3aa562a17dd@implements.be>
References: <6243ad910c02150d526b7b32d4cfef9d@implements.be>
<42ADAE10.6050204@archonet.com>
<93fcaa35413e2059526ab3aa562a17dd@implements.be>
> Ok, if all 21 are affected, I can understand the problem.
> But allow me to say that this is a "functional error"
It's a choice between total throughput on a high load, high connection
basis (MVCC dramatically wins here), versus a single user, low load
scenario (MS Access is designed for this).
Believe me when I say that a lot of people have spent a lot of time
explicitly making the system work that way.
> On 13 Jun 2005, at 18:02, Richard Huxton wrote:
>
> Yves Vindevogel wrote:
> I forgot cc
> Begin forwarded message:
> From: Yves Vindevogel
> <yves.vindevogel@implements.be>
> Date: Mon 13 Jun 2005 17:45:19 CEST
> To: Tom Lane <tgl@sss.pgh.pa.us>
> Subject: Re: [PERFORM] Updates on large tables
> are extremely slow
>
> Yes, but if I update one column, why should PG
> update 21 indexes ?
> There's only one index affected !
>
> No - all 21 are affected. MVCC creates a new row on disk.
>
> --
> Richard Huxton
> Archonet Ltd
>
>
> Met vriendelijke groeten,
> Bien à vous,
> Kind regards,
>
> Yves Vindevogel
> Implements
>
>
>
> ______________________________________________________________________
>
>
>
> Mail: yves.vindevogel@implements.be - Mobile: +32 (478) 80 82 91
>
> Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
>
> Web: http://www.implements.be
>
> First they ignore you. Then they laugh at you. Then they fight you.
> Then you win.
> Mahatma Ghandi.
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq--
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pg@rbt.ca, yves.vindevogel@implements.be
Subject: Re: Updates on large tables are extremely slow
In-Reply-To: <1118681599.723.105.camel@home>
* 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