Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New postgresql.conf still has stats_temp_directory in new Postgres 16 instance #65

Open
ijmorlan opened this issue Jun 4, 2024 · 1 comment

Comments

@ijmorlan
Copy link

ijmorlan commented Jun 4, 2024

I was able to correct this by removing the stats_temp_directory setting from /usr/local/etc/postgresql-common/createcluster.conf. I'm not sure the best resolution of this; in the long run, I think it's clear stats_temp_directory should not be configured in the default createcluster.conf, but pre-16 versions are still current so it might be premature to remove it now. On the other hand, if I do a default installation and then use pg_createcluster to create a PG16 instance, it's surprising for it not start due to an obsolete setting in the newly-created postgresql.conf.

Regardless, I'm grateful for being able to use postgresql-common on Mac OS. I don't know how anybody can use PG for development without it.

@hollyroberts
Copy link

I had a similar issue at the time when PG15 came out (which removed the parameter). It was down to the version 189 in postgresql-common.rb which needed to be at least 241. Looking at the debian tracker stable is now 248 so maybe this just needs bumping, but I don't know what the extra effects will be. It's certainly a large increase of several years worth of changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants