Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%)
От | Adrian Klaver |
---|---|
Тема | Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%) |
Дата | |
Msg-id | 29e2642f-cfc7-e120-0dc1-0b064ccfac32@aklaver.com обсуждение исходный текст |
Ответ на | Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%) (Julie Nishimura <juliezain@hotmail.com>) |
Ответы |
Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%)
|
Список | pgsql-general |
On 5/28/19 11:20 AM, Julie Nishimura wrote: > What is the impact of fsm_relatiosn being maxed out? > It has been awhile since I thought about this as these settings are no longer relevant as of 8.4: https://www.postgresql.org/docs/8.4/release-8-4.html " Track free space in separate per-relation "fork" files (Heikki) Free space discovered by VACUUM is now recorded in *_fsm files, rather than in a fixed-sized shared memory area. The max_fsm_pages and max_fsm_relations settings have been removed, greatly simplifying administration of free space management. " To get to your question, I would take a look at: https://www.postgresql.org/docs/8.3/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-FSM Pay attention to the embedded link in the above: https://www.postgresql.org/docs/8.3/kernel-resources.html#SYSVIPC -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: