 | |
#41
 
| |||
| |||
|
Re: annotated postgresql.conf -
10-24-2008
, 07:31 AM
|
My question is: is it a runtime parameter for the kernel? do I have to recompile it? If I do it am I in risk to break the system? |
#42
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#43
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#44
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#45
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#46
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#47
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#48
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#49
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. |
how to set parameters related to the available RAM, only default values
are listed:
http://www.postgresql.org/docs/8.3/s...-resource.html
Some months ago an Oracle DBA just told me that Postgres it is nice but
it has default memory parameters set so low that you cannot use it as it
comes out of the box in a serious (high load) production environment.
So I am looking for some (fast) tips on how to increase memory
utilization in order to speed up performances and autovacuum (is it
turned on by default in 8.3 right?) and to reduce datafiles
fragmentation by tweaking max_fsm_pages and maintenance_work_mem.
Sure, it would be nice if Postgres could balance all those esotic
parameters accepting just one parameter, the maximum allowed memory usage
#50
| |||
| |||
|
|
There _is_ a good tutorial, and that is the PostgreSQL documentation: http://www.postgresql.org/docs/curre...resources.html Actually, the hint is pretty helpful, isn't it? In all likelyhood wou will have to increase SHMMAX. Yours, Laurenz Albe |
I tried following the hints and kept increasing or changing differnet
parameters. But the server just would not come up.
Even just increasing the maximum number of connections to 300 will not
work for me and the server will not come up.
I think PostgreSQL is an excellent database system and I use it for all
my projects. I just think the configuration part is its weakest point.
I would prefer PostgreSQL to do a system analysis and have a global
preference setting (say: dedicated server, maximum performance, minimum
footprint) and choose its own optimal settings.
A utility program that can modify an existing configuration file based
on user demands like: use more memory, allow N connections etc. will
work for me as well.
A good second would be publishing a number of sample configuration files
on the website for common configurations.
A server not coming up leaving some message in a system log is NOT a
helpful hint.
Regards,
Silvio Bierman
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.