Hi Richard,
I've tested again according your suggestion. I noticed that for each
time the pgsql slow down, there is a short period a process called "pdflush"
eating up lot of I/O. I've goolgled and know it is a process for writing
dirty pages back to the disk by the Linux kernel. I will have f
Sachchida Ojha wrote:
> Hi,
>
> I am new to PostgreSQL database. Can anybody help me (or point me the
> related post) to install PostgreSQL on windows XP from command line.
> (From .bat file)
http://pginstaller.projects.postgresql.org/silent.html
//Magnus
---(end of broa
Hi,
I am new to PostgreSQL database. Can anybody help me (or point me the
related post) to install PostgreSQL on windows XP from command line.
(From .bat file)
Thanks
Sachi
"Dolafi, Tom" <[EMAIL PROTECTED]> writes:
> In version 8.1.5, I have an rtree index on a 1.5 GB table. The size of
> this index is 500 MB. After migrating to 8.2.3, the size of this index
> has increased to 35GB. I've dropped are recreated the index and got the
> same result. In 8.2.3 the index
>>> On Thu, Jun 28, 2007 at 1:54 AM, in message
<[EMAIL PROTECTED]>, "Ho Fat Tsang"
<[EMAIL PROTECTED]> wrote:
>
> I don't know why the server occasionally
> slow down a bit for every 3 minutes.
If the problem is checkpoints, try making your background writer more
aggressive. This allows mor
"Greg Smith" <[EMAIL PROTECTED]> writes:
> On Thu, 28 Jun 2007, Ho Fat Tsang wrote:
>
>> I have tuned the checkpoint_timeout to 30 second which is ten times less than
>> default and the issue is still reproduced.
>
> Your problem looks exactly like a pause at every checkpoint, and I'm not
> sure w
On Thu, 28 Jun 2007, Ho Fat Tsang wrote:
I have tuned the checkpoint_timeout to 30 second which is ten times less
than default and the issue is still reproduced.
Doing a checkpoint every 30 seconds is crazy; no wonder your system is
pausing so much. Put the timeout back to the default. What
On Wed, 27 Jun 2007, Evan Reiser wrote:
For some reason our database seems to have trouble handling 10+ inserts
per second which seems to be a pretty trivial load for this hardware,
we're seeing very high %iowait
Two things come to mind:
1) Is the table you're inserting into very complicated
we've tried benchmarking the array, the data array can write at
800mb/s for files less than 256mb (raid write cache), after which it
can sustain 300mb/s, it seems like it can also handle 6-700 iops when
benchmarking. it seems to work as expected outside of postgres, I
guess we can look at the driv
Jean-David Beyer wrote:
Chris wrote (in part):
I didn't have logging set up before but it's up and running now and I
was getting
LOG: checkpoints are occurring too frequently (26 seconds apart)
HINT: Consider increasing the configuration parameter
"checkpoint_segments".
So I increased that
Jean-David Beyer wrote:
I have not used postgreSQL since I tried it once in about 1998 (when I found
it unsatisfactory, but much has changed since then), but I am going to try
it again. What would be a good checkpointing interval? I would guess 26
seconds is too often. What considerations go into
Chris wrote (in part):
> I didn't have logging set up before but it's up and running now and I
> was getting
>
> LOG: checkpoints are occurring too frequently (26 seconds apart)
> HINT: Consider increasing the configuration parameter
> "checkpoint_segments".
>
> So I increased that from 10 to
Ho Fat Tsang wrote:
Hi Richard,
Thank for your prompt reply. I have used the command "vmstat 10" to
investigate the I/O issue and listed below :
procs ---memory-- ---swap-- -io --system--
cpu
r b swpd free buff cache si sobibo incs us
Hi Richard,
Thank for your prompt reply. I have used the command "vmstat 10" to
investigate the I/O issue and listed below :
procs ---memory-- ---swap-- -io --system--
cpu
r b swpd free buff cache si sobibo incs us sy id
wa
0 0 26848
Richard Huxton wrote:
Chris wrote:
db=# UPDATE email_upd_test SET domainname=substring(email from
position('@' in email));
UPDATE 100
Time: 43796.030 ms
I think I'm I/O bound from my very limited understanding of vmstat.
Well, 43 seconds to update 1 million rows suggests your real query
Ho Fat Tsang wrote:
Hi Richard,
I have tuned the checkpoint_timeout to 30 second which is ten times less
than default and the issue is still reproduced. Do you have any recommended
configuration for WAL ?
If you look at the output of "vmstat 10" and "iostat -m 10" (I'm
assuming you're on Li
Hi Richard,
I have tuned the checkpoint_timeout to 30 second which is ten times less
than default and the issue is still reproduced. Do you have any recommended
configuration for WAL ?
Thanks
Twinsen
2007/6/28, Richard Huxton <[EMAIL PROTECTED]>:
Ho Fat Tsang wrote:
>
> I am new for postg
Ho Fat Tsang wrote:
I am new for postgresql server. And now i work on a projects which
requires postgreSQL 8.0 and Java. I don't know why the server occasionally
slow down a bit for every 3 minutes.
Do anyone can help me about this ? or any resolution for a sudden
performance degrade ( beca
Two points:
* need more information about the circumstances.
* could it be that autovaccum hits you?
Andreas
-- Ursprüngl. Mitteil. --
Betreff:[PERFORM] PostgreSQL 8.0 occasionally slow down
Von:"Ho Fat Tsang" <[EMAIL PROTECTED]>
Datum: 28.06.2007 06:56
Hi,
I am new fo
Evan Reiser wrote:
I was wondering if you guys have some suggested settings for our server, i
think we are not hardware limited but the configureation is set up
incorrectly. For some reason our database seems to have trouble handling
10+ inserts per second which seems to be a pretty trivial load
Chris wrote:
db=# UPDATE email_upd_test SET domainname=substring(email from
position('@' in email));
UPDATE 100
Time: 43796.030 ms
I think I'm I/O bound from my very limited understanding of vmstat.
Well, 43 seconds to update 1 million rows suggests your real query
should be complete in
21 matches
Mail list logo
