Re: Auto-tuning work_mem and maintenance_work_mem

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: "MauMau" <maumau307(at)gmail(dot)com>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>, "Josh Berkus" <josh(at)agliodbs(dot)com>
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Date: 2013-10-10 14:52:19
Message-ID: m2y56189gc.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"MauMau" <maumau307(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-10-10 14:59:58 Re: Auto-tuning work_mem and maintenance_work_mem
Previous Message Robert Haas 2013-10-10 14:51:17 Re: [COMMITTERS] pgsql: Revive line type