Re: Wait events monitoring future development - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: Wait events monitoring future development
Date
Msg-id 0A3221C70F24FB45833433255569204D1F5C01F2@G01JPEXMBYT05
Whole thread Raw
In response to Re: Wait events monitoring future development  (Satoshi Nagayasu <snaga@uptime.jp>)
Responses Re: Wait events monitoring future development  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
From: pgsql-hackers-owner@postgresql.org
> I used to think of that this kind of features should be enabled by default,
> because when I was working at the previous company, I had only few features
> to understand what is happening inside PostgreSQL by observing production
> databases. I needed those features enabled in the production databases when
> I was called.
> 
> However, now I have another opinion. When we release the next major release
> saying 10.0 with the wait monitoring, many people will start their benchmark
> test with a configuration with *the default values*, and if they see some
> performance decrease, for example around 10%, they will be talking about
> it as the performance decrease in PostgreSQL 10.0. It means PostgreSQL will
> be facing difficult reputation.
> 
> So, I agree with the features should be disabled by default for a while.

I understand your feeling well.  This is a difficult decision.  Let's hope for trivial overhead.

Regards
Takayuki Tsunakawa



pgsql-hackers by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: Wait events monitoring future development
Next
From: Thomas Munro
Date:
Subject: Re: dsm_unpin_segment