Search endpoint uses reader connection even though it writes to db

[p1c2u]

Hi,

I have set up connection with reader/writer with reader to have read-only access and the app is using reader connection even search is trying to write to db. I use version 3.0.0. I have readonly mode turned off.

Thanks

[vincentsarago]

search is trying to write to db.

why do you say this?

On a search request, pgstac will write the requested search request in the search_table: https://github.com/stac-utils/pgstac/blob/6da165b7c4f6da321d0b58bbb78da2887763a0d8/src/pgstac/sql/004_search.sql#L686-L745

This can be avoided if you set your pgstac database as read-only https://stac-utils.github.io/pgstac/pgstac/#read-only-mode

Technically it's not stac-fastapi-pgstac trying to write to the db but pgstac itself writing to it

[p1c2u]

I just want the app to respect reader/writer connection pools.

On a search request, pgstac will write the requested search request in the search_table: https://github.com/stac-utils/pgstac/blob/6da165b7c4f6da321d0b58bbb78da2887763a0d8/src/pgstac/sql/004_search.sql#L686-L745

Exactly, that's why I propose it should use writer connection pool.

This can be avoided if you set your pgstac database as read-only https://stac-utils.github.io/pgstac/pgstac/#read-only-mode

I mentioned that I have readonly mode turned off because I want to be able to write to it.

Technically it's not stac-fastapi-pgstac trying to write to the db but pgstac itself writing to it

However stac-fastapi-pgstac decides which connection (reader or writer) to use and it this case it uses incorrect one.