counts tracks - Search results in mailing lists

2024-04-05 08:07:35 | [MASSMAIL]Managing replication lag (Jonathan Schaeffer)

track_counts = on track_functions = pl autovacuum = on datestyle = 'iso, mdy' timezone = 'UTC' lc_messages

2024-02-02 11:25:12 | Postgres 16 slow "fast" shutdown when using streaming replication (Stefan Kohlhauser)

track_counts | on | configuration file unix_socket

2021-03-31 16:22:09 | Re: Performance bottleneck. High active sessions but postmaster kernel threads are in a sleep state (Hotmail)

track of the wait events in another grafana graph. We use the following query to generate the graph. (We assume that an active session that has a NULL wait_event is "ON CPU”.  Not sure

2020-03-03 08:34:42 | Re: Autovacuum/Analyze Doesn't seem to be running properly (Laurenz Albe)

track_counts" parameters set to on? - Hitting 90% of autovacuum_freeze_max_age is no problem

2019-11-24 12:53:19 | performance degredation after upgrade from 9.6 to 12 (Mariel Cherkassky)

track_activity_query_size = 32764 maintenance_work_mem = 250MB work_mem = 32MB shared_buffers = 8058MB effective_cache_size = 16116MB in 12v I also added the following settings : log_directory = 'pg_log' enable_partitionwise_join

2019-11-24 12:53:19 | performance degredation after upgrade from 9.6 to 12 (Mariel Cherkassky)

track_activity_query_size = 32764 maintenance_work_mem = 250MB work_mem = 32MB shared_buffers = 8058MB effective_cache_size = 16116MB in 12v I also added the following settings : log_directory = 'pg_log' enable_partitionwise_join

2019-03-04 18:23:33 | Re: [External] Re: postgresql11 space reuse under high delete/update rate (Vijaykumar Jain)

track the progress of vacuum by this table (pg_stat_progress_vacuum) https:///docs/10/progress-reporting.html pgtesting=# select * from pg_stat_progress_vacuum; -[ RECORD 1 ]------+-------------- pid | 9575 datid | 16384 datname | pgtesting relid | 16446 phase | scanning heap heap

2018-12-03 17:35:54 | Re: pg_stat_all_tables data isnt accurate (Nikolay Samokhvalov)

counts to the collector just before going idle; so a query or transaction still in progress does not affect the displayed totals. Also, the collector itself emits a new report at most once per PGSTAT

2018-03-25 04:07:05 | bloatcheck.sql (A System Admin)

track_counts to also be on. log_autovacuum_min_duration = 0 # MIQ Value; #log_autovacuum

2017-03-22 01:05:13 | [ADMIN] (Santiago DIEZ)

track_counts" option. 2017-03-21 22:34:03 CET LOG: database system was shut

2017-01-12 01:46:52 | Re: [ADMIN] vacuum toast loop? (Tom Lane)

count then there might be some reason to worry. If you weren't seeing any verbose output at all, there would be much more reason to worry. (FWIW, as of 9.6 or thereabouts there

2016-05-06 10:12:59 | Autovacuums not triggering anymore (Thomas SIMON)

track_counts is on, and autovacuum launcher process is working. Below autovacuums parameters : "autovacuum";"on" "autovacuum

2015-08-11 08:38:16 | Postgresql-9.1 CentOS7 effective_cache_size issue (Michael H)

track_counts = on track_functions = all log_parser_stats = off log_planner_stats = off log_executor

2015-07-31 04:44:42 | Re: Autovacuum behavior (Om Prakash Jaiswal)

track_count = on;It is missing. RegardsOm Prakash On Friday, 31 July 2015 12:21 AM, John

2015-07-22 02:16:38 | Auto Vacuum Daemon not running even though it's been configured (Wei Shan)

track_counts; track_counts -------------- on *Verification:* *Step 1:* [root@tiffany1 ~]# grep autovacuum /var/log/messages *Step 2:* [root