From: Kevin Barnard <kevin.barnard@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Table UPDATE is too slow
Date: Sun, 5 Sep 2004 20:19:35 -0500
Message-ID: <b068057c040905181998476d1@mail.gmail.com> (raw)
In-Reply-To: <413BA104.1040508@geizhals.at>
References: <4134BF36.3000504@syscor.com>
<413BA104.1040508@geizhals.at>
Do all of the commands to swap tables in a transaction. The table
gets locked briefly but should have a lot less impact then the update
command.
On Mon, 06 Sep 2004 01:28:04 +0200, Marinos J. Yannikos <mjy@geizhals.at> wrote:
>
> That said, I'm not entirely sure how well postgres' client libraries can
> deal with tables being renamed while in use, perhaps someone can shed
> some light on this.
>
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: kevin.barnard@gmail.com
Subject: Re: Table UPDATE is too slow
In-Reply-To: <b068057c040905181998476d1@mail.gmail.com>
* 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