From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Query on Postgresql performance |
Date: | 2003-09-04 10:40:54 |
Message-ID: | 20030904104054.GA1178@libertyrms.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Sep 03, 2003 at 12:32:42PM -0700, Naveen Palavalli wrote:
> My server spawns a new connection to Postgresql foreach client. My
I don't think you want to do that. You should use a pool. Back end
startup is mighty expensive.
> 1) Effects related to Vaccum :- I performed 10 trials of adding and
> deleting entries . In each trial , 1 client adds 10,000 entries
> and then deletes them . During the course of these 10 trials ,
You'll want to vacuum after every set of deletes, I should think. If
you're woking in more than one transaction for the deletes, then
fairly frequent vacuums of that table will be effective.
> I was using Postgresql 7.3.3 earlier but it kept crashing the
> database after a Vaccum . So I switched to a older and stabler
> version 7.2.4
You don't want to use 7.3.3. It has a rare but serious bug and was
replaced in something like 24 hours with 7.3.4. The 7.2 branch is no
longer being maintained, so you really probably should use the 7.3
branch. I'm unaware of others having stability problems with 7.3.4,
so if you see them, you should find your core dump and talk to the
people on -hackers.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2003-09-04 11:01:53 | Re: SELECT's take a long time compared to other DBMS |
Previous Message | Relaxin | 2003-09-04 08:16:47 | Re: SELECT's take a long time compared to other DBMS |