Sean Gillespie

Yes, this was superceded by changes @kderme did to prepare sanchonet releases

> How will this help in future forks? I don't think it will help directly. > Will be a stale leftover when we are on Conway across all networks? There...

There's still an HLint failure: https://ci.iog.io/build/3779994/nixlog/1

Which version of Postgresql are you using?

I think this must be your problem. In the latest release we added some migrations that are only valid using Postgres 12+. I created some instructions here: https://github.com/IntersectMBO/cardano-db-sync/blob/13.2.0.1/doc/upgrading-postgresql.md. I also...

I'm pretty sure it's _supposed_ to work, based on the doc here: https://github.com/IntersectMBO/cardano-db-sync/blob/master/doc/migrations.md#upgrading-to-1320x. I was able to upgrade from 13.1.1.3 -> 13.2.0.1 (although I have not verified the data integrity)....

The following warning should also be looked at: ``` cardano-db-sync-post-stop[131443]: yes: standard output: Broken pipe ``` Although it does not prevent the snapshot from being created

> Great work! Good to merge when it's tested on preprod or preview. It can't be tested in preprod or preview right? Also, I forgot to update the comment, I...

> Right, it would only work on sanchonet after rebasing to master Yes, this is how I was able to test it on sanchonet. I applied my changes on top...

Hi @PalluWeb, you should be able to change the cabal target `cardano-db-sync` to `cardano-db-sync:exe:cardano-db-sync`. As for the index state warning, running `cabal update` should clear that