POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used: 79569of 80000 (99%) - Mailing list pgsql-general

From Julie Nishimura
Subject POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used: 79569of 80000 (99%)
Date
Msg-id BYAPR08MB5014E38BF2FE704F56546BCFAC020@BYAPR08MB5014.namprd08.prod.outlook.com
Whole thread Raw
Responses Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%)
Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%)
Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%)
List pgsql-general
Hello,
We have an issue with fsm_relations utilization reaching 99%, I was able to vacuum a handful of tables, but it wasn't enough to make a noticeable difference. I think at this point we will need to increase the number of fsm_relations from 80,000 to 100,000 which will require a restart. Because there aren't any more dead rows to delete. I confirmed this by connecting to each db and running the following query:
SELECT relname, n_live_tup, n_dead_tup from pg_stat_user_tables order by n_dead_tup desc
daily_mail_shared_state_cddt_3588-
relname | n_live_tup | n_dead_tup
----------------+------------+------------
article_errors | 0 | 0
article_names | 3375193 | 0
indexdefs | 0 | 0
tabledefs | 0 | 0

Above output, shows n_dead_tup is zeroed out, this makes me believe that we need to increase the number of fsm relations to a number between 90k and 100k.But I might be wrong, need your advice.

PostgreSQL 8.2.15 (Greenplum Database 4.3.8.1 build 1)

Thanks!

pgsql-general by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: terminating walsender process due to replication timeout
Next
From: Julie Nishimura
Date:
Subject: Re: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used:79569 of 80000 (99%)