From 3ade3d10c109b333edd6f0f52c6d35d09f95c131 Mon Sep 17 00:00:00 2001 From: "blooym.dev" Date: Fri, 21 Aug 2026 17:35:46 +0000 Subject: [PATCH] docs: clarify the postgres seq fix command There was a syntax error in this command, so I updated the doc to clarify it and also show it needs an integer, not a string like it implied before. --- docs/3_DEBUGGING_YOUR_SETUP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/3_DEBUGGING_YOUR_SETUP.md b/docs/3_DEBUGGING_YOUR_SETUP.md index b1e6906..80944cb 100644 --- a/docs/3_DEBUGGING_YOUR_SETUP.md +++ b/docs/3_DEBUGGING_YOUR_SETUP.md @@ -19,4 +19,4 @@ Fixing this isn't too hard. You want to figure out what `seq` the relays think y > > #protip double check that the `seq` is actually misaligned with your PDS by getting the latest `seq` from your PDS using PDSls's firehose feature and a cursor value of `0` when connecting. If the relays don't have a `seq` that's bigger than your PDSs `seq` then this isn't your issue! -Now you need to update the PDS to use a `seq` that's *at least* one above the highest `seq` any of the relays have. Currently doing this on Tranquil depends on your used storage backend. For the default Postgres repo store you want to shutdown Tranquil itself, open the DB in `psql` and run `SELECT setval('firehose_seq, ');` and the start Tranquil back up. Take a few actions to make sure new events get sent out. Everything should work once all the downstream consumers have had a chance to resync. You can double check with debug.hose.cam that all the relays show your PDS as `active`. Some might need a lil push with a request crawl, luckily debug.hose.cam also makes that easy :p (ignore that it says it failed to issue a request crawl, CORS is fickle). +Now you need to update the PDS to use a `seq` that's *at least* one above the highest `seq` any of the relays have. Currently doing this on Tranquil depends on your used storage backend. For the default Postgres repo store you want to shutdown Tranquil itself, open the DB in `psql` and run `SELECT setval('firehose_seq', );` and the start Tranquil back up. Take a few actions to make sure new events get sent out. Everything should work once all the downstream consumers have had a chance to resync. You can double check with debug.hose.cam that all the relays show your PDS as `active`. Some might need a lil push with a request crawl, luckily debug.hose.cam also makes that easy :p (ignore that it says it failed to issue a request crawl, CORS is fickle).