Wednesday, September 25, 2019

[google-cloud-sql-discuss] log_error_verbosity set to terse but error log has entire query

Hi, 

I have a postgres function which is returning an error to my application if the data is old and i have a newer version already in db (idempotency check). 
for one execution of this function it is generating a log message that is spread to over 50 individual logs. 
This is polluting my db-logs and there is no way to filter it out in stack-trace

I tried enabling  log_error_verbosity flag and set it to 'terse' but this is not helping as well. still I am seeing these logs.

Is it a bug or I am doing something wrong?

three issues . 
  1. log message spread to ~ 50 log entries
  2. log_error_verbosity not working as expected
  3. log message is also coming as info and not error 
  4. Screenshot 2019-09-25 at 2.31.09 PM.png




--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/8df7b24e-62e7-41a9-9f7f-aa3b226f8ecd%40googlegroups.com.

No comments:

Post a Comment