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

From MauMau
Subject Re: Auto-tuning work_mem and maintenance_work_mem
Date
Msg-id F8491E91CE11402D97AFD3EAC2074D54@maumau
Whole thread Raw
In response to Re: Auto-tuning work_mem and maintenance_work_mem  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Auto-tuning work_mem and maintenance_work_mem  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
From: "Dimitri Fontaine" <dimitri@2ndQuadrant.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




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Next
From: Robert Haas
Date:
Subject: Re: logical changeset generation v6.2