On Sun, Jun 25, 2017 at 9:27 AM, rajan <vgmonnet@xxxxxxxxx> wrote:
Actually I did not make any changes to postgresql.conf
When studying about this parameter I thought I should check what my current
setting(for maintenance_work_mem) is and then I found that it is commented
in postgresql.conf while the pg_settings has the value enabled.
-----
--
Thanks,
Rajan.
--
View this message in context: http://www.postgresql-archive.org/pg9-6-maintenance-work- mem-is-disabled-in-postgresql- conf-but-running-a-select- query-for-pg-settingsd- tp5968586p5968596.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
maintenance_work_mem isn't a setting that can be completely disabled. It's used for normal maintenance operations like autovaccum and index creation. If not set in postgresql.conf, it has a default value of 64MB in 9.6
https://www.postgresql.org/docs/9.6/static/runtime-config-resource.html
https://www.postgresql.org/docs/9.6/static/runtime-config-resource.html
Keith
