Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
For questions about cardano-db-sync, one of the core Cardano components, which provides a convenient way to find and query historical information from the Cardano blockchain through the use of a Structured Query Language (SQL) relational database.
0
votes
DB Sync deleting blocks up to slot operation running for 10+ hours
Apparently, the DB sync process just takes a really long time to "initiate". Not sure if that is the right term, but I will use it for now.
I just checked the db-sync status and it has completed the …
0
votes
2
answers
50
views
Detailed upgrade instructions for latest db-sync release 13.1
I was wondering if anyone knows where I can find the detailed upgrade instructions for db-sync 13.1. I’m current on the previous release and think the upgrade shouldn’t be too difficult, but I can fi …
1
vote
5
answers
174
views
DB Sync deleting blocks up to slot operation running for 10+ hours
I recently created a new server and install of Cardano node and db sync (1.34.1 & 12.0.2) on same machine. I implemented the snapshot restore to bring the Postgres DB up to EPOCH 325 and was able to s …
0
votes
0
answers
28
views
Receiving "Handling input offset" message during db sync 3.1.1.3 update - going on 20 hours ...
Performing db sync update to 3.1.1.3 and waiting while server processes fix. Currently receiving Handling input offset message as part of SQL update, been running for approximately 20 hours now. Is …
1
vote
1
answer
66
views
DB Sync Upgrade to v 3.1.1.3 snapshot restore (4 days old) running "extra migration consumed...
Interested to understand why db sync snap shot does not include new consumed_tx_out column. Just upgraded to v3.1.1.3 using manual method (not docker) and restored most recent db snapshot from 4 days …