Closed charalamm closed 8 months ago
@charalamm with that debugging information, I'm not able to tell what is going on here as the psycopg trace does not include the SQL that was resulting in the error.
The tests are definitely creating a fresh database and are able to run the base migration, so I'm not sure what could be different on your system. Could you try running the base migration manually on a fresh database without pgstac installed? (On a fresh install, this is all that pypgstac migrate is doing behind the scenes)
psql -f /home/.../.venv/lib/python3.11/site-packages/pypgstac/migrations/pgstac.0.8.4.sql
@charalamm I think that I have tracked this down as an issue that is with RDS that does not show up on regular Postgres relative to how RDS sets up the rds_superuser. I'm still trying to track this down specifically to figure out a fix.
I have a fresh postgres and I am trying to install pgstac via pygstac.
I installed
pypgstac[psycopg]==v0.8.4
and runpypgstac migrate --debug
but I getI started reducing the version and finally pgstac got installed with
pypgstac==v0.8.1
.Then I installed again 0.8.4 and run
pypgstac migrate --debug
but I get the same error. Finally I run in the dbGRANT pgstac_ingest TO user;
and thenpypgstac migrate
with 0.8.4 and it worked, however I am wondering if the manual command can cause any problems