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
