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
I'm struggling to identify the SQL queries produced by stac-fastapi-pgstac. From what I've gathered, asyncpg utilizes prepared statements. This explains why, when I inspect the pg_stat_activity table, the entries appear in a format like this:
postgis=> SELECT datname, pid, state, query, age(clock_timestamp(), query_start) AS age
FROM pg_stat_activity
WHERE state <> 'idle'
AND query NOT LIKE '% FROM pg_stat_activity %'
ORDER BY age;
datname | pid | state | query | age
---------+-------+--------+------------------------------------------------------------+-----------------
postgis | 28867 | active | +| 00:00:00.09398
| | | SELECT * FROM search($1::text::jsonb);+|
| | | |
postgis | 18963 | active | +| 00:00:00.126161
| | | SELECT * FROM search($1::text::jsonb);+|
| | | |
(2 rows)
How can I see the actual SQL statements? Does it make sense to add logging.debughere?
The text was updated successfully, but these errors were encountered:
I'm struggling to identify the SQL queries produced by
stac-fastapi-pgstac
. From what I've gathered, asyncpg utilizes prepared statements. This explains why, when I inspect thepg_stat_activity
table, the entries appear in a format like this:How can I see the actual SQL statements? Does it make sense to add
logging.debug
here?The text was updated successfully, but these errors were encountered: