Sorry the double and top post, but please disregard. I've been informed by a coworker that this is a PostgreSQL limitation on the length of the current_query column and that thus far, the PostgreSQL devs will not change it.
Sorry for the trouble. /alex On Mar 4, 9:56 am, Alex Ezell <[email protected]> wrote: > We often do diagnostics on our PostgreSQL systems by looking at > currently running queries with some sql like this: > > select procpid, to_char((now() - query_start), 'HH24:MI:SS.MS') as > query_time, client_addr as client_host, current_query > from pg_stat_activity > where current_query not ilike '<idle>' > order by query_time desc; > > However, since we've moved to sqlalchemy, we've found that we can no > longer see the full text of the current_query because of all the > aliasing that sqlalchemy does in its select statements. Has anyone had > this issue or know of any workarounds whether they be sqlalchemy-based > or in postgres? > > Sorry if this is completely off-topic. I'm just at a loss for where to > turn. > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
