Skip site navigation (1) Skip section navigation (2)

Re: Large database help

From: xbdelacour(at)yahoo(dot)com
To: Ragnar Kjørstad <postgres(at)ragnark(dot)vestdata(dot)no>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Large database help
Date: 2001-04-24 00:15:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
ANote: some disk activety should be expected. Maybe postgresql updates
>the log? Or at the very least it will update the atime timestamps for
>the files everytime they're read. This shouldn't cause enough disk
>activity to become a performance-problem, but if I remember your initial
>post correctly, you indicated that one processor was fully saturated.
>Maybe the problem is in fact related to locking and smp, and not related
>to shared-memory and disk activity?

Then, please correct me if I'm wrong: I should be able to test your 
hypothesis by creating a small DB (of say 2MB) and setting up at least a 
dozen backends to tag it. If I get the same symptoms w/ respect to disk 
activity/performance then we could say that the problem is not related to 
shared memory/the amount of data/swapping.

What log files are output from postgres? I was under the impression that 
postmaster's stdout/stderr were the only output. I've been postmaster 
xyz >& log.txt'ing it. I'll check into this.

Thanks a lot for your help :-)


Do You Yahoo!?
Get your free address at

In response to


pgsql-admin by date

Next:From: Tom LaneDate: 2001-04-24 00:24:16
Subject: Re: Large database help
Previous:From: Ragnar KjørstadDate: 2001-04-24 00:06:26
Subject: Re: Large database help

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group