| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Julie Nishimura <juliezain(at)hotmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used: 79569 of 80000 (99%) |
| Date: | 2019-05-28 19:43:20 |
| Message-ID: | 29e2642f-cfc7-e120-0dc1-0b064ccfac32@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julie Nishimura | 2019-05-28 21:03:44 | Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used: 79569 of 80000 (99%) |
| Previous Message | Andreas Kretschmer | 2019-05-28 18:47:39 | Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used: 79569 of 80000 (99%) |