Re: Cannot turn track_counts on

2025-06-25 Thread Anton Shepelev
I wrote: > I have a Postgres sever with the 'track_counts' setting > stuck in 'off'. [...] I ghosted-out from this thread with my tail between my legs, because the only collegue who had access to the affected machine had no time to spare and then went of vacation. He has returned now, and I hav

Re: Cannot turn track_counts on

2025-04-22 Thread Adrian Klaver
On 4/22/25 01:31, Anton Shepelev wrote: Adrian Klaver: There is something different about your setup, as here on Ubuntu(which uses the Debian packaging) I see: [...] Yes. It is on on your side, and pgsql shows NULL values as NULL. Can the latter be due to a differnce in Postgres versions

Re: Cannot turn track_counts on

2025-04-22 Thread Anton Shepelev
Adrian Klaver: > Anton Shepelev: > > > Have you any further ideas how to turn track_counts on? > > It is matter of finding out what is setting?: > > source | override Indeed, I having begun with this crucial question. > There is something different about your setup, as here on > Ubuntu(

Re: Cannot turn track_counts on

2025-04-21 Thread Adrian Klaver
On 4/21/25 09:46, Anton Shepelev wrote: I wrote: I will test if clearing shared_preload_libraries and restarting Postgres has any effect on track_counts, just in case. Nope, it didn't unstick track_counts: db=# show shared_preload_libraries ; -[ RECORD 1 ]+- shared_prelo

Re: Cannot turn track_counts on

2025-04-21 Thread Adrian Klaver
On 4/21/25 09:26, Anton Shepelev wrote: Adrian Klaver: Found it. It is coming from the Debian postgresql-common packaging. /usr/bin/pg_config is wrapper that contains: #!/bin/sh # If postgresql-server-dev-* is installed, call pg_config from the latest # available one. Otherwise fall back t

Re: Cannot turn track_counts on

2025-04-21 Thread Anton Shepelev
I wrote: > I will test if clearing shared_preload_libraries and > restarting Postgres has any effect on track_counts, just > in case. Nope, it didn't unstick track_counts: db=# show shared_preload_libraries ; -[ RECORD 1 ]+- shared_preload_libraries | db=# select * from pg_s

Re: Cannot turn track_counts on

2025-04-21 Thread Anton Shepelev
Adrian Klaver: > Found it. It is coming from the Debian postgresql-common > packaging. > > /usr/bin/pg_config is wrapper that contains: > > #!/bin/sh > > # If postgresql-server-dev-* is installed, call pg_config from the latest > # available one. Otherwise fall back to libpq-dev's version. Ah,

Re: Cannot turn track_counts on

2025-04-18 Thread Adrian Klaver
On 4/17/25 15:25, Anton Shepelev wrote: Adrian Klaver to Anton Shepelev: Yet that is what we get for `pg_config --version' on the affected system. A nearly identical error message seems to come up while installing psycopg2 -- a Python library for Postgres, e.g.:

Re: Cannot turn track_counts on

2025-04-18 Thread Anton Shepelev
Adrian Klaver to Anton Shepelev: > >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/postgre

Re: Cannot turn track_counts on

2025-04-17 Thread Anton Shepelev
Adrian Klaver to Anton Shepelev: > The below does not look like a Postgres message to me. > > > You need to install postgresql-server-dev-NN for > > building a server-side extension or libpq-dev for > > building a client-side application. Yet that is what we get for `pg_config --version' on the a

Re: Cannot turn track_counts on

2025-04-17 Thread Anton Shepelev
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? It is a normal installation on a Linux machine, and my company has full root access to it over SSH. Because of strict security measures, however, only a

Re: Cannot turn track_counts on

2025-04-17 Thread Adrian Klaver
On 4/17/25 14:23, Anton Shepelev wrote: Adrian Klaver to Anton Shepelev: db=# show shared_preload_libraries; shared_preload_libraries --- online_analyze, plantuner Are you running PostgresPro? Both those modules are associated with it: https://postg

Re: Cannot turn track_counts on

2025-04-17 Thread Adrian Klaver
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 variable

Re: Cannot turn track_counts on

2025-04-17 Thread Adrian Klaver
On 4/17/25 07:23, Tom Lane wrote: Anton Shepelev writes: What extensions do you have installed? Nothing much: db=# show shared_preload_libraries; shared_preload_libraries --- online_analyze, plantuner Never heard of either of those, but just from th

Re: Cannot turn track_counts on

2025-04-17 Thread Tom Lane
Anton Shepelev writes: >> What extensions do you have installed? > Nothing much: > db=# show shared_preload_libraries; >shared_preload_libraries > --- >online_analyze, plantuner Never heard of either of those, but just from the names, they sound like they mig

Re: Cannot turn track_counts on

2025-04-17 Thread Anton Shepelev
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 >

Re: Cannot turn track_counts on

2025-04-17 Thread Ron Johnson
On Thu, Apr 17, 2025 at 5:13 AM Anton Shepelev wrote: > 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? > > It is a normal installation on a Linux machine, and my > company has full root access

Re: Cannot turn track_counts on

2025-04-17 Thread Anton Shepelev
Adrian Klaver: > Anton Shepelev: > > > have a Postgres sever with the 'track_counts' > > setting stuck in 'off'. > > [...] > > name| track_counts > > setting | on > > source | override > > This shows a setting of 'on' not the 'off' you mention in > the first paragraph. I beg pardon. Having n

Re: Cannot turn track_counts on

2025-04-16 Thread Adrian Klaver
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

Re: Cannot turn track_counts on

2025-04-16 Thread Adrian Klaver
On 4/16/25 02:27, Anton Shepelev wrote: Hello, all. I have a Postgres sever with the 'track_counts' setting stuck in 'off'. I cannot seem to enable it with either of a. ALTER SYSTEM, b. ALTER DATABASE, c. ALTER USER, d. or plain SET. pg_settings shows: name| track_counts

Re: Cannot turn track_counts on

2025-04-16 Thread Daniel Gustafsson
> On 16 Apr 2025, at 16:53, Tom Lane wrote: > > Anton Shepelev writes: >> pg_settings shows: > >> name| track_counts >> setting | on >> source | override > >> What does 'override' mean in the 'source' column? How can I >> find where in the system this setting is overridden? > > I am

Re: Cannot turn track_counts on

2025-04-16 Thread Tom Lane
Anton Shepelev writes: > pg_settings shows: > name| track_counts > setting | on > source | override > What does 'override' mean in the 'source' column? How can I > find where in the system this setting is overridden? I am fairly certain that there is nothing in core Postgres that wo

Cannot turn track_counts on

2025-04-16 Thread Anton Shepelev
Hello, all. I have a Postgres sever with the 'track_counts' setting stuck in 'off'. I cannot seem to enable it with either of a. ALTER SYSTEM, b. ALTER DATABASE, c. ALTER USER, d. or plain SET. pg_settings shows: name| track_counts setting | on source | override What does 'o