On Thu, Aug 4, 2016 at 4:41 PM, Tsunakawa, Takayuki <tsunakawa.ta...@jp.fujitsu.com> wrote: > 1. The performance gain is huge. > 2. It's almost useless because we can only see the postgres command line with > Process Explorer, which the user must download from Microsoft and install. > 3. I don't see the benefit of update_process_title=on at the expense of > performance. > 4. The default setting of PostgreSQL parameters should be friendly. I'm > afraid many users cannot track the cause of poor performance to > update_process_title. I heard that MySQL's popularity was partly because it > ran smoothly on Windows in the early days. PostgreSQL should be, too. > > The question is, do we want to change the default to off on other OSes?
I don't think so. > Is the command line really useful? > If useful, does it need to be on by default? I'd vote for keeping it on by default, because this information with ps is really useful for any kind of deployments, testing, etc. Here is a different proposal: documenting instead that disabling that parameter on Windows can improve performance, at the cost of losing information verbosity for processes. -- Michael -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers