powa-team/pg_stat_kcache

pg 15 compatibility

Closed this issue · 7 comments

shared_preload_libraries = '...,pg_stat_kcache,...'
pg_ctl -w start
waiting for server to start....2022-07-01 06:45:51.050 UTC [190] LOG:  Auto detecting pg_stat_kcache.linux_hz parameter...
2022-07-01 06:45:51.050 UTC [190] LOG:  pg_stat_kcache.linux_hz is set to 1000000
2022-07-01 06:45:51.051 UTC [190] FATAL:  cannot request additional shared memory outside shmem_request_hook
2022-07-01 06:45:51.051 UTC [190] LOG:  database system is shut down
pg_ctl: could not start server
rjuju commented

This was properly handled a month and a half ago with 1f9fb67, released in version 2.2.1 (https://github.com/powa-team/pg_stat_kcache/releases/tag/REL2_2_1).

I got this error with master up to date branch

rjuju commented

I just tried with latest pg15 commit and latest pg_stat_kcache commit and it works:

=# select version();
                                                             version
---------------------------------------------------------------------------------------------------------------------------------
 PostgreSQL 15beta2@1201e0f038 [...]
(1 row)

=# show shared_preload_libraries ;
     shared_preload_libraries
-----------------------------------
 pg_stat_statements,pg_stat_kcache
(1 row)

Can you confirm the current commit you're using for pg_stat_kcache? If 1f9fb67 is not included, you need to refresh your local repo. If it's, my best bet is that you have other extensions in your shared_preload_libraries with one of that that isn't compatible with pg15.

you have other extensions in your shared_preload_libraries with one of that that isn't compatible with pg15

OK, thanks, I will find such extensions

you have other extensions in your shared_preload_libraries with one of that that isn't compatible with pg15

OK, thanks, I will find such extensions

It was https://github.com/EnterpriseDB/pldebugger

rjuju commented

Ok, thanks for the confirmation!

I didn't know that pldebugger had to be in shared_preload_libraries, otherwise I would have fixed it when the new hook was added.

this issue also solved my problem, thanks