Difference between revisions of "Esxi og vCenter"
(→vcenter postgresql) |
|||
| Line 6: | Line 6: | ||
On installation vCenter sets a number of config overrides in <datadir>/postgresql.conf.auto - pay attention to <code>work_mem</code> and <code>temp_buffers</code> - they might be set lower than postgresql default values (which is quite silly imho.) which will limit performance of postgresql - espesically when querying performance counters. | On installation vCenter sets a number of config overrides in <datadir>/postgresql.conf.auto - pay attention to <code>work_mem</code> and <code>temp_buffers</code> - they might be set lower than postgresql default values (which is quite silly imho.) which will limit performance of postgresql - espesically when querying performance counters. | ||
| − | + | ==launch psql== | |
start psql client with <code>/opt/vmware/vpostgres/current/bin/psql -h localhost -U postgres</code> | start psql client with <code>/opt/vmware/vpostgres/current/bin/psql -h localhost -U postgres</code> | ||
Revision as of 22:01, 26 June 2017
vcenter postgresql
Disclaimer: describes vcenter 6.0 - it may vary for other versions ?
vcenter uses an embedded postgresql installation. Binaries are located in /opt/vmware/vpostgres/current/bin - data and config files are located in /storage/db/vpostgres/
On installation vCenter sets a number of config overrides in <datadir>/postgresql.conf.auto - pay attention to work_mem and temp_buffers - they might be set lower than postgresql default values (which is quite silly imho.) which will limit performance of postgresql - espesically when querying performance counters.
launch psql
start psql client with /opt/vmware/vpostgres/current/bin/psql -h localhost -U postgres
