Обсуждение: [ADMIN] pg9.6 - maintenance_work_mem is disabled in postgresql.conf byrunning a select query for pg_settings returns it is enabled
Hi, maintenance_work_mem is commented in postgresql.conf #maintenance_work_mem = 64MB but the following query, select * from pg_settings where name = 'maintenance_work_mem'; returns the following. Does it means it is enabled? name | maintenance_work_mem setting | 65536 unit | kB category | Resource Usage / Memory short_desc | Sets the maximum memory to be used for maintenance operations. extra_desc | This includes operations such as VACUUM and CREATE INDEX. context | user vartype | integer source | default min_val | 1024 max_val | 2147483647 enumvals | boot_val | 65536 reset_val | 65536 sourcefile | sourceline | pending_restart | f ----- -- Thanks, Rajan. -- View this message in context: http://www.postgresql-archive.org/pg9-6-maintenance-work-mem-is-disabled-in-postgresql-conf-by-running-a-select-query-for-pg-settings-d-tp5968586.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
Hi ,
Have you restarted after commenting this parameter.
Thanks.
On Jun 25, 2017 1:23 PM, "rajan" <vgmonnet@gmail.com> wrote:
Hi,
maintenance_work_mem is commented in postgresql.conf
#maintenance_work_mem = 64MB
but the following query,
select * from pg_settings where name = 'maintenance_work_mem';
returns the following. Does it means it is enabled?
name | maintenance_work_mem
setting | 65536
unit | kB
category | Resource Usage / Memory
short_desc | Sets the maximum memory to be used for maintenance
operations.
extra_desc | This includes operations such as VACUUM and CREATE INDEX.
context | user
vartype | integer
source | default
min_val | 1024
max_val | 2147483647
enumvals |
boot_val | 65536
reset_val | 65536
sourcefile |
sourceline |
pending_restart | f
-----
--
Thanks,
Rajan.
--
View this message in context: http://www.postgresql-archive.org/pg9-6-maintenance-work- mem-is-disabled-in-postgresql- conf-by-running-a-select- query-for-pg-settings-d- tp5968586.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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.
On Sun, Jun 25, 2017 at 9:27 AM, rajan <vgmonnet@gmail.com> 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@postgresql.org)
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
Lines in postgresql.conf being commented out doesn't mean things are disabled, it means the default value is not overridden. > On Jun 25, 2017, at 1:53 AM, rajan <vgmonnet@gmail.com> wrote: > > Hi, > > maintenance_work_mem is commented in postgresql.conf > > #maintenance_work_mem = 64MB > > but the following query, > > select * from pg_settings where name = 'maintenance_work_mem'; > > returns the following. Does it means it is enabled? > > name | maintenance_work_mem > setting | 65536 > unit | kB > category | Resource Usage / Memory > short_desc | Sets the maximum memory to be used for maintenance > operations. > extra_desc | This includes operations such as VACUUM and CREATE INDEX. > context | user > vartype | integer > source | default > min_val | 1024 > max_val | 2147483647 > enumvals | > boot_val | 65536 > reset_val | 65536 > sourcefile | > sourceline | > pending_restart | f -- Scott Ribe scott_ribe@elevated-dev.com (303) 722-0567
It's keep some memories default to perform system operations.
Thanks.
On Jun 25, 2017 6:58 PM, "rajan" <vgmonnet@gmail.com> 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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Thanks all for replies. Now I understand.
On 25 Jun 2017 19:53, "Ashish Tiwari" <tashish786@gmail.com> wrote:
It's keep some memories default to perform system operations.Thanks.On Jun 25, 2017 6:58 PM, "rajan" <vgmonnet@gmail.com> 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-con f-but-running-a-select-query- for-pg-settingsd-tp5968586p596 8596.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
You're welcome!
On Jun 25, 2017 8:06 PM, "Muthiah Rajan" <vgmonnet@gmail.com> wrote:
Thanks all for replies. Now I understand.On 25 Jun 2017 19:53, "Ashish Tiwari" <tashish786@gmail.com> wrote:It's keep some memories default to perform system operations.Thanks.On Jun 25, 2017 6:58 PM, "rajan" <vgmonnet@gmail.com> 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-con f-but-running-a-select-query-f or-pg-settingsd-tp5968586p5968 596.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin