support PostgreSQL 16 about postgresql HOT 5 CLOSED

In 2023, the first work was to push pg14 and pg15, as quickly as possible, with in background "the backward compatibility ".
I think that your proposal to cleanup is what needs to be done.
I like the idea postgresql_vacuum_cost_page_miss: "{{ 2 if postgresql_version is version_compare('14', '>=') else 10 }}"

from postgresql.

Hi @conscribtor , Thanks for your work. I think this change need more discussions, but i definitively think that you should ensure backward compatibility. We doesn't provide default configuration template for many reasons, most of them I don't know very well but you can check on olders PR / issues. People here can certainly give you much more information about the reasons of all theses changes. As you probably seen on our recent changes, we don't test pg =< 10 anymore.
@tsoulabail Can you give us your opinion about this ?

from postgresql.

Adding a new PostgreSQL version might be a good opportunity to fix those defaults. There might be ways to include them while remaining backwards compatible.

One possibility might be to version_compare('16', '>=') them, but use the annotations to reflect when they were originally changed upstream:

postgresql_vacuum_cost_page_miss:  "{{ 2 if postgresql_version is version_compare('16', '>=') else 10 }}" # (<= 13: 10, >= 14: 2) 0-10000 credits

Let me know what you think, if i should proceed with that idea and which I should include in that way.

from postgresql.

In 2023, the first work was to push pg14 and pg15, as quickly as possible, with in background "the backward compatibility ". I think that your proposal to cleanup is what needs to be done. I like the idea postgresql_vacuum_cost_page_miss: "{{ 2 if postgresql_version is version_compare('14', '>=') else 10 }}"

Thank you - I've pushed the new defaults using this pattern in 5562199.

from postgresql.

I close this issue, work can be seen in #564

from postgresql.