pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Radovan Antloga <radovan.antloga@siol.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance decrease
Date: Thu, 20 Apr 2006 12:00:07 -0500
Message-ID: <20060420170007.GA49405@pervasive.com> (raw)
In-Reply-To: <015801c66494$ee3d25c0$1e4ba8c0@AR6>
References: <011b01c6648e$067ee170$1e4ba8c0@AR6>
	<18973.1145547701@sss.pgh.pa.us>
	<015801c66494$ee3d25c0$1e4ba8c0@AR6>

On Thu, Apr 20, 2006 at 06:10:21PM +0200, Radovan Antloga wrote:
> I have once or twice a month update on many records (~6000) but
> not so many. I did not expect PG would have problems with
> updating 15800 records.

And generally speaking, it doesn't. But you do need to ensure that
you're vacuuming the database frequently enough. Autovacuum is a good
way to do that.

> My test was on Windows XP SP2.
> I have AMD 64 2.1 GHz cpu with
> 1GB ram.

One think to keep in mind is that the windows code is rather new, so it
is possible to find some performance issues there.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (5+ messages)  latest in thread

Message-ID: <20060420170007.GA49405@pervasive.com>
Permalink:  ../20060420170007.GA49405@pervasive.com/
Also on:    postgresql.org/message-id/20060420170007.GA49405@pervasive.com

 · 

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: jnasby@pervasive.com, radovan.antloga@siol.net, tgl@sss.pgh.pa.us
  Subject: Re: Performance decrease
  In-Reply-To: <20060420170007.GA49405@pervasive.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