Closed Deltaus closed 11 months ago
I shall put it on Jan's TODO list to make the plprofiler compatible with pg16. I suspect that this will be easy for him to accomplish and that we'll do this in the very near future. Most defintely before pg16 GA in the fall, probably sooner.
We are starting on this project (thank you AsifR and Jan) and we hope to version 4.4.2 supporting pg16 within 10 days or so
Got it, thank you!
I can confirm that 4.4.2 builds against v16.
Thanks Devrim. I'm also building it against pg15 & pg16 in the pgEdge environment.
On Tue, Aug 1, 2023 at 6:33 AM Devrim Gündüz @.***> wrote:
I can confirm that 4.4.2 builds against v16.
— Reply to this email directly, view it on GitHub https://github.com/bigsql/plprofiler/issues/16#issuecomment-1660038265, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMWOHRHNSSPXISTQRPJCLDXTDLPDANCNFSM6AAAAAAZN4PUGA . You are receiving this because you commented.Message ID: @.***>
done in 4.4.2
:-)
Recently when I tried to build this extension with latest postgres 16, it threw errors like below
After some investigation, I think it's because community changed definition of Int64GetDatumFast https://github.com/postgres/postgres/commit/c8b2ef05f481ef06326d7b9f3eb14b303f215c7e#diff-eacba6996e6eb6b6a80a36b056cb95fa3ca94b57d8a30cb5de6bffd251687fafR897 from:
to:
while in plprofiler code, the variable is uint64 https://github.com/bigsql/plprofiler/blob/master/plprofiler.h#L160
Is it possible that this issue get fixed in the future release? And when can I expect a postgres16 compatible version to be released? Thank you!