Michael Paquier

> Does it mean the query string normalization column on the hint table will be removed and the query_id column will be added on the table instead? Yes, it means...

> I don't understand the issue with normalized query strings in detail, but if you are having trouble with it, Duplication. The normalization code in pg_hint_plan is a copy-paste of...

> I'm not sure how much we rely on having the normalised query string available (either in this extension or pg_plan_asvsr), but if for some reason pgss isn't an option...

> This is just on real-world case in which having a queryId will be very useful. There are other cases such as adding whitespace or a linebreak in the query...

> The problem here is two things like: 1. reducing the bloat of the hint table by long query text 2. reducing the costs of normalization string Is my understanding...

I have begun my butcher work for this release, and began with two things: 1. Stabilization of the regression tests. A few things have changed in upstream, for the best...

> So, It's okay from us. :-D If you have any questions, we can talk about that on Friday in live.

> What is the status in here? v17 beta2 is already out. Still need a bit of time, but I am towards a release by the end of August with...

Looking at my calendar, I am proposing the 29th of August for the tarball release. @devrimgunduz

The branches have been structured and prepared for the upcoming release, and a new PG17 branch has been created with a github action job for automated tests. At this point...