Re: Auto-tuning work_mem and maintenance_work_mem

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Dimitri Fontaine" <dimitri(at)2ndQuadrant(dot)fr>
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-15 12:47:55
Message-ID: F8491E91CE11402D97AFD3EAC2074D54@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: "Dimitri Fontaine" <dimitri(at)2ndQuadrant(dot)fr>
> The reason why that parameter default has changed from 5 to 0 is that
> some people would mistakenly use a prepared transaction without a
> transaction manager. Few only people are actually using a transaction
> manager that it's better to have them have to set PostgreSQL.

I guess this problem is not unique to PostgreSQL. I think PostgreSQL can be
more friendly for normal users (who use external transaction manager), and
does not need to be too conservative because of people who do irregular
things.

Regards
MauMau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-10-15 12:49:26 Re: logical changeset generation v6.2
Previous Message Andres Freund 2013-10-15 12:42:45 Re: Auto-tuning work_mem and maintenance_work_mem