Thread: How do I adjust max_fsm_pages
Hi, My postgresql configuration is max_locks_per_transaction = 256 max_connections = 200 shared_buffers = 6000 max_fsm_pages = 200000 max_fsm_relations = 1500 My serversers total RAM=32GB Still I am not able to insert more than 10million records, its taking lot of time. It also gives hint to increse max_fsm_pages. So Please suggest me how do I adjust above parameters to avoid errors and to increase postgres speed performance? Thanks , Amar
When last did you do a FULL vacuum and analyse the stats report at the end?
On 1/2/90, amar buwa <amar.buwa@hovservices.com> wrote:
Hi,
My postgresql configuration is
max_locks_per_transaction = 256
max_connections = 200
shared_buffers = 6000
max_fsm_pages = 200000
max_fsm_relations = 1500
My serversers total RAM=32GB
Still I am not able to insert more than 10million records, its
taking lot of time. It also gives hint to increse max_fsm_pages.
So Please suggest me how do I adjust above parameters to avoid errors
and to increase postgres speed performance?
Thanks ,
Amar
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
I use to do FULL vacuum every day. The additional info is its postgresql-8.1.3.
Thanks,
Amar
adey wrote:
Thanks,
Amar
adey wrote:
When last did you do a FULL vacuum and analyse the stats report at the end?On 1/2/90, amar buwa <amar.buwa@hovservices.com> wrote:Hi,
My postgresql configuration is
max_locks_per_transaction = 256
max_connections = 200
shared_buffers = 6000
max_fsm_pages = 200000
max_fsm_relations = 1500
My serversers total RAM=32GB
Still I am not able to insert more than 10million records, its
taking lot of time. It also gives hint to increse max_fsm_pages.
So Please suggest me how do I adjust above parameters to avoid errors
and to increase postgres speed performance?
Thanks ,
Amar
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match