Re: [HACKERS] Reporting query on crash even if completed
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Reporting query on crash even if completed |
Дата | |
Msg-id | CA+TgmoYV+vfOGAU7kXm20AP8MSWkEgfWW=E8gFLS3esJdxWa_w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Reporting query on crash even if completed (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Reporting query on crash even if completed
Re: [HACKERS] Reporting query on crash even if completed |
Список | pgsql-hackers |
On Mon, Sep 18, 2017 at 9:47 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Now, for pg_stat_activity part of the argument why this wouldn't be > confusing was that you could also see the "state" field. Maybe we > should try to shoehorn equivalent info into the crash log entry? Yeah, I think so. Really, I think this is an inadvertency, and thus a bug. But instead of just not showing the query when the backend is idle, I'd change the display for that case to: DETAIL: Failed process was idle; last query was: %s Or something like that. I guess we'd need another case for a backend that crashed without ever running a query. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: