-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems using seperate postgres reader/writer hosts with pgstac #4
Comments
confirmed here that search is not a read-only operation: The problem may be here: https://github.com/stac-utils/stac-fastapi-pgstac/blob/main/stac_fastapi/pgstac/core.py#L163 Because |
Now that stac-utils/pgstac#215 is merged. Does that fix this issue? Is there anything that needs to be done to make use of it? |
As far as I understand, |
I was able to get it to work in RDS. You have to use one of the pre-release 3.0 versions of stac-fastapi-pgstac, then update the pgstac setting |
What version of pgSTAC did you have to use, @jbeezley ? I don't quite understand what is the right combination for make it happen. |
Looks like 3.0 of |
Ported from stac-utils/stac-fastapi#370.
Original Issue:
I'm running into problems when using pgstac with separate reader and writer hosts (in my case an Aurora cluster). Search endpoints return an error similar to the following:
The issue appears to be that the SQL functions defined by pgstac for searching perform operations that require write access (select for update, create temp table, etc). But, the search endpoints connect to the DB through the
readpool
https://github.com/stac-utils/stac-fastapi/blob/5dc8e0eb63d9cc07663968ed5ed9505e753bf298/stac_fastapi/pgstac/stac_fastapi/pgstac/core.py#L119-L120
This is not a problem when a single host is used for both read and write, as in the docker compose yaml. https://github.com/stac-utils/stac-fastapi/blob/5dc8e0eb63d9cc07663968ed5ed9505e753bf298/docker-compose.yml#L47-L48
When
POSTGRES_HOST_READER
points to a host that is truly read-only, however, this becomes a problem.The text was updated successfully, but these errors were encountered: