| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Printing backtrace of postgres processes |
| Date: | 2022-01-26 05:36:55 |
| Message-ID: | CALj2ACXaNthMJXHFWVvNQz+pnMYSL3ySTMO8LgWoS=JN7j-hPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 25, 2022 at 12:00 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> Thanks for the comments, attached v17 patch has the fix for the same.
Have a minor comment on v17:
can we modify the elog(LOG, to new style ereport(LOG, ?
+ elog(LOG_SERVER_ONLY, "current backtrace:%s", errtrace.data);
/*----------
* New-style error reporting API: to be used in this way:
* ereport(ERROR,
* errcode(ERRCODE_UNDEFINED_CURSOR),
* errmsg("portal \"%s\" not found", stmt->portalname),
* ... other errxxx() fields as needed ...);
*
Regards,
Bharath Rupireddy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-01-26 06:29:29 | Re: GUC flags |
| Previous Message | torikoshia | 2022-01-26 05:28:43 | Re: pg_log_backend_memory_contexts() and log level |