pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Alex Wang <alex@alexwang.com>
Cc: Csaba Nagy <nagy@ecircle-ag.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: VERY slow after many updates
Date: Mon, 21 Nov 2005 10:43:38 -0600
Message-ID: <1132591417.28788.7.camel@state.g2switchworks.com> (raw)
In-Reply-To: <006b01c5ed04$f640ef70$0200a8c0@alexxp>
References: <002601c5ecdd$503279e0$0200a8c0@alexxp>
	<1132398732.10890.480.camel@coppola.muc.ecircle.de>
	<005201c5ed01$7f15c310$0200a8c0@alexxp>
	<1132402372.10890.487.camel@coppola.muc.ecircle.de>
	<006b01c5ed04$f640ef70$0200a8c0@alexxp>

On Sat, 2005-11-19 at 06:29, Alex Wang wrote:
> Great infomation. I didn't know that update is equal to delete+insert in 
> Postgres. I would be more careful on designing the database access method in 
> this case.

Just make sure you have regular vacuums scheduled (or run them from
within your app) and you're fine.  

view thread (7+ messages)

Message-ID: <1132591417.28788.7.camel@state.g2switchworks.com>
Permalink:  ../1132591417.28788.7.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1132591417.28788.7.camel@state.g2switchworks.com

copy link · copy postgr.es

reply

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: smarlowe@g2switchworks.com, alex@alexwang.com, nagy@ecircle-ag.com
  Subject: Re: VERY slow after many updates
  In-Reply-To: <1132591417.28788.7.camel@state.g2switchworks.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