Re: Auto-tuning work_mem and maintenance_work_mem - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Auto-tuning work_mem and maintenance_work_mem
Date
Msg-id m2y56189gc.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Auto-tuning work_mem and maintenance_work_mem  ("MauMau" <maumau307@gmail.com>)
Responses Re: Auto-tuning work_mem and maintenance_work_mem
List pgsql-hackers
"MauMau" <maumau307@gmail.com> writes:
> Although this is not directly related to memory, could you set
> max_prepared_transactions = max_connections at initdb time?  People must

You really need to have a transaction manager around when issuing
prepared transaction as failing to commit/rollback them will prevent
VACUUM and quickly lead you to an interesting situation.

It used to have a default of 5 and is now properly defaulting to 0.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Revive line type
Next
From: Bruce Momjian
Date:
Subject: Re: Auto-tuning work_mem and maintenance_work_mem