Re: << unrecognized configuration parameter "pg_stat_statements.track" >>

From: Andres Freund <andres(at)anarazel(dot)de>
To: otheus uibk <otheus(dot)uibk(at)gmail(dot)com>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: << unrecognized configuration parameter "pg_stat_statements.track" >>
Date: 2016-01-27 14:54:04
Message-ID: 20160127145404.GD17919@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2016-01-27 15:49:22 +0100, otheus uibk wrote:
> What a doozie! Documenting such a requirement in such a fashion (at the end
> of of a section) is a golden example of obfuscation and
> cryptodocumentation. Perhaps someone with wisdom will see fit to move the
> relevant paragraph to the top of the "Configuration parameters" section,
> instead of at the end.

Meh. It used to be general requirement to add extension prefixes to
custom_variable_classes, it wasn't pg_stat_statement specific. And it's
a short paragraph.

But either way, 9.1 is soon to be EOLed, I don't see much point in
working on its docs.

Andres

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-01-27 16:11:29 Re: BUG #13892: SELECT FALSE = FALSE = TRUE; error
Previous Message otheus uibk 2016-01-27 14:49:22 Re: << unrecognized configuration parameter "pg_stat_statements.track" >>