>> Recently I've discovered that if there are multiple values of the same >> parameter in postgresql.conf PostgreSQL will silently use the last one. >> It looks like not the best approach to me. For instance, user can find >> the first value in the config file and expect that it will be used, etc. >> >> I suggest to warn users about duplicated parameters. Here is a >> corresponding patch. >> >> Thoughts? > > -1 - I frequently just override earlier parameters by adding an include > at the end of the file. Also, with postgresql.auto.conf it's even more > common to override parameters.
-1 from me too by the same reason Andres said. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
