Re: 7.1.3 : copy from stdin is very slow! - Mailing list pgsql-general

From Chris Gamache
Subject Re: 7.1.3 : copy from stdin is very slow!
Date
Msg-id 20020207133216.70204.qmail@web13803.mail.yahoo.com
Whole thread Raw
In response to Re: 7.1.3 : copy from stdin is very slow!  (Justin Clift <justin@postgresql.org>)
Responses Re: 7.1.3 : copy from stdin is very slow!
List pgsql-general
It didn't balk at the 2*max_connections, but I changed it to 128 anyway. I
stopped the import after 34 hours... I shutdown and restarted the postmaster,
hoping the new config values would make a difference. It seems very strange
that I was able to import this data into my 7.0.3 database in under three
hours. It would seem the same import is taking longer by several orders of
magnitude with 7.1.3.

There is one difference that I might make note of. Before (7.0.3) I used a
mount point for the data drive of /usr/local/pgsql/data/base/ ... I have since
moved the mount point up one level ... /usr/local/pgsql/data/ ... So data/
resides on the same drive that base/ does (7.1.3). It seemed more logical to do
it that way. However, I have heard that by moving the pg_xlog to a different
drive the performance is increased. I can't confirm this in the documentation,
though.

I'm still at a loss for what could be going on.

--- Justin Clift wrote:
>
>
> Chris Gamache wrote:
> <snip>
>
> > shared_buffers = 2*max_connections
>
> This looks interesting.  I thought the "2*max_connections" was supposed
> to be a commented line?
>
> Chris, do you really have the line :
>
> shared_buffers = 2*max_connections
>
> in your postgresql.conf, uncommented and all?  I'm thinking that somehow
> PostgreSQL might actually be accepting it, and interpreting it as the #
> 2.
>
> And THAT would crawl.
>
> You should instead (by hand), get the value of your max_connections
> parameter (in the same .conf file), double it, and that's the lowest
> number you should use.
>
> i.e.
>
> if max_connections = 32, then you should be using shared_buffers of at
> least 64.
> if max_connections = 120, then you should be using shared_buffers of at
> least 240.
>
> etc.
>
> Hope that's helpful.
>
> :-)
>
> Regards and best wishes,
>
> Justin Clift
>
>
> <snip>
> > ...
> > Still crawling. I thought I understood properly the idea for removing
> fsync,
> > and increasing the buffer and wal settings. No effect on the insert, tho...
> >
> > Any ideas or advice welcome!
> >
> > CG
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Send FREE Valentine eCards with Yahoo! Greetings!
> > http://greetings.yahoo.com
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
>
> --
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
>    - Indira Gandhi
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html



__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com

pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: Dream Server?
Next
From: Jeff Eckermann
Date:
Subject: Re: Build problems with 7.2