Open RealOrangeOne opened 1 year ago
We are looking into providing configurability of log_min_error_statement
. This might be small enough effort that we could deliver soon. As soon as we have clear plan, we will update.
Thank you for raising this @RealOrangeOne!
Required Terms
What service(s) is this request for?
Heroku Postgres
Tell us about what you're trying to solve. What challenges are you facing?
Under certain conditions, such as when queries error for unexpected reasons, Heroku Postgres will include the full query with the log. These queries may contain sensitive data (in some cases, PII), which it would be ideal to keep out of our log streams.
Because the query can spread into multiple log lines, it's not possible for to filter this as it's ingested into logs easily.
PostgreSQL claims this can be configured with the
log_min_error_statement
setting, currently set toERROR
. Having the ability to increase this (toPANIC
) should remove these queries from the logs, albeit at the cost of being unable to see query information when there are issues.Raising here as recommended from support ticket.