From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Anton Shepelev <anton(dot)txt(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cannot turn track_counts on |
Date: | 2025-04-17 15:17:19 |
Message-ID: | 1a99f488-9d24-41d1-a1a5-17ea4ce87899@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/17/25 07:05, Anton Shepelev wrote:
> Tom Lane to Anton Shepelev:
>
>>> I have a Postgres sever with the 'track_counts' setting
>>> stuck in 'off'. [...]
>>
>> I am fairly certain that there is nothing in core Postgres
>> that would do that. PGC_S_OVERRIDE is used to lock down
>> the values of certain variables that shouldn't be allowed
>> to change, but track_counts surely isn't one of those.
>> And a quick grep through the code finds nothing applying
>> PGC_S_OVERRIDE to it.
>
> Thanks for checking it, Tom.
>
>> What extensions do you have installed?
>
> Nothing much:
>
> db=# show shared_preload_libraries;
> shared_preload_libraries
> ---------------------------
> online_analyze, plantuner
Are you running PostgresPro?
Both those modules are associated with it:
https://postgrespro.com/docs/postgrespro/17/contrib.html
If you are you might want to talk to their tech support.
>
> db=# \dx
> List of installed extensions
> Name | Version | Schema | Description
> ---------+---------+------------+------------------------------
> plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Anton Shepelev | 2025-04-17 21:23:07 | Re: Cannot turn track_counts on |
Previous Message | Adrian Klaver | 2025-04-17 15:16:58 | Re: Cannot turn track_counts on |