-
Notifications
You must be signed in to change notification settings - Fork 300
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
SQL query logging #595
Comments
Yeah, I haven't needed it. I use pg_stat_statements..
… On 13 May 2023, at 13.22, cayter ***@***.***> wrote:
Is there a reason why this library doesn't accept logger for logging the SQL queries with time consumed? The suggested approach <#368 (comment)> here doesn't work as the underlying function returns a Promise and the same method is also used for building the query.
—
Reply to this email directly, view it on GitHub <#595>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ2RVNF6YAHGFZCWBEGBSLXF5VGLANCNFSM6AAAAAAYAN6D3I>.
You are receiving this because you are subscribed to this thread.
|
I'm just wondering if there's a plan to add this as it'd be useful for OpenTelemetry to trace the query so that we don't have to wrap another layer or manually trace everywhere we call postgres method that runs the query. |
There's some work on this now - I'm tracking it in #461 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a reason why this library doesn't accept logger for logging the SQL queries with time consumed? The suggested approach here doesn't work as the underlying function returns a Promise and the same method is also used for building the query.
The text was updated successfully, but these errors were encountered: