You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Versions
The db-sync version (eg cardano-db-sync --version): 13.2.0.1
PostgreSQL version: 16.2
Build/Install Method
The method you use to build or install cardano-db-sync: Release binaries
Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): systemd
Additional context
The file scripts/postgresql-setup.sh is currently lagging in compatibility:
When using disable-ledger flag, we do not expect to have lstate files, but absence of lstate file would break the script
As raised in Restoring from snapshot error - role "cexplorer" does not exist #1659, when using exit-on-error flag against pg_restore, we now need to specify --no-owner and --role=<role> which wasnt required before, this role may need to be devised from PGPASSFILE (for socket, that would mean current user) OR it could be accepted as command line argument.
The snapshots should also contain the config to be able to easily identify compatibility for that snapshot with the flags that can be used.
L112 assumes psql listing of particular database can be counted by filter "${PGDATABASE} " , tho it's common to add prefix to the datbase name, would be safer to have space on either side " ${PGDATABASE} ".
Versions
The
db-sync
version (egcardano-db-sync --version
): 13.2.0.1PostgreSQL version: 16.2
Build/Install Method
The method you use to build or install
cardano-db-sync
: Release binariesRun method
The method you used to run
cardano-db-sync
(eg Nix/Docker/systemd/none): systemdAdditional context
The file
scripts/postgresql-setup.sh
is currently lagging in compatibility:disable-ledger
flag, we do not expect to have lstate files, but absence of lstate file would break the scriptexit-on-error
flag against pg_restore, we now need to specify--no-owner
and--role=<role>
which wasnt required before, thisrole
may need to be devised from PGPASSFILE (for socket, that would mean current user) OR it could be accepted as command line argument.count=$(psql -l "${PGDATABASE}" | grep " ${PGDATABASE} " | cut -d \| -f 3 | grep -c UTF8)
The text was updated successfully, but these errors were encountered: