upgrading config db metric table from v4.1 to v5.2

[seanzechman]

When we deployed v4.1 (as an upgrade from v2 ) - we started by creating empty pgwatch and measurement databases. These were populated automatically with tables like pgwatch.metric when the pgwatch service was started which was great, nothing to do manually.

We are now in the process of upgrading to v5,2 and we initially tried just truncating the metric table and starting the service, hoping it would populate the pgwatch.metric table but that didn't work. The upgrade documentation (https://pgwat.ch/v5.x/tutorial/upgrading.html#updating-the-metrics-collector) states to run /etc/pgwatch/sql/config_store/metric_definitions.sql pgwatch - but that file does not exist.

How can we get our backend config database to get the newer metrics? - I have been looking for stat_statements_jit metric as verification which was identified as a new feature in v5.0.0 release notes.

Thank you for your time.

[seanzechman]

Any ideas? @pashagolub @0xgouda ?

[pashagolub]

That definitely shouldn't be there. True.

[pashagolub]

The easiest way would be to erase the whole schema and start with an empty database. Since you already truncated all the metrics

[seanzechman]

I was suspecting that would work but was trying to not have to readd all the sources, so was hoping that maybe there was another way. Thanks for all your work on this project!