From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Anton Shepelev <anton(dot)txt(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cannot turn track_counts on |
Date: | 2025-04-16 18:07:37 |
Message-ID: | 32b6d55b-e1bb-4300-86bc-b24036414a8f@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/16/25 09:25, Anton Shepelev wrote:
> Adrian Klaver:
>> Anton Shepelev:
>>
>> This shows a setting of 'on' not the 'off' you mention in
>> the first paragraph.
>
> I beg pardon. Having no immediate access to the system in
> question, I confess to having mocked up those results from
> an analogous query on our reference system. Here is the
> actual result from the affected server (db name changed):
>
> db=# select * from pg_settings where name = 'track_counts';
> -[ RECORD 1 ]---+--------------------------------------------------
> name | track_counts
> setting | off
> unit |
> category | Statistics / Query and Index Statistics Collector
> short_desc | Collects statistics on database activity.
> extra_desc |
> context | superuser
> vartype | bool
> source | override
> min_val |
> max_val |
> enumvals |
> boot_val | on
> reset_val | off
> sourcefile |
> sourceline |
> pending_restart | f
>
> It was very wrong of me so to misinform you.
>
Per post from Daniel Gustafsson:
"Also, is this by any chance a managed instance like Amazon RDS or
Azure, or is it a local database under your control?"
And from Tom Lane:
"What extensions do you have installed?"
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2025-04-16 18:43:59 | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |
Previous Message | Achilleas Mantzios | 2025-04-16 17:35:26 | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |