stone-age maintenance procedures ;-)
От | Ulrich Wisser |
---|---|
Тема | stone-age maintenance procedures ;-) |
Дата | |
Msg-id | 412DB7C4.4050704@relevanttraffic.se обсуждение исходный текст |
Ответы |
Re: stone-age maintenance procedures ;-)
|
Список | pgsql-general |
Hi, lately I've been acused of "stone-age maintenance procedures". Hopefully I will find some help to develop from stone-age to roman empire. ;-) To optimize the performance and to minimize the maintainance needs I would like to ask you guys about some values in my postgresql.conf. select version(); PostgreSQL 7.3.4 on i386-redhat-linux-gnu, compiled by GCC i386-redhat-linux-gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) (1 row) max_connections = 32 superuser_reserved_connections = 2 shared_buffers = 30000 max_fsm_relations = 10000 max_fsm_pages = 100000 max_locks_per_transaction = 128 wal_buffers = 32 sort_mem = 1024 vacuum_mem = 8192 checkpoint_segments = 16 # in logfile segments, min 1, 16MB each fsync = false open_datasync effective_cache_size = 20000 # typically 8KB each The total database size on disk is ~6GB. Some tables get changed *very* frequently. A nightly "vacuum full analyze" frees about 250,000 rows on each of three tables. And yes I will change to 7.4 this week. TIA Ulrich -- ------------------------------------------------------------ Relevant Traffic AB, Riddargatan 10, 11435 Stockholm, Sweden Tel. +46-8-6789750 http://www.relevanttraffic.se
В списке pgsql-general по дате отправления: