Re: Printing backtrace of postgres processes
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Greg Stark <stark@mit.edu>
Cc: vignesh C <vignesh21@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, torikoshia <torikoshia@oss.nttdata.com>, pgsql-hackers@lists.postgresql.org
Date: 2022-03-30T16:03:08Z
Lists: pgsql-hackers
Attachments
On Wed, Mar 30, 2022 at 11:53:52AM -0400, Greg Stark wrote: > Sadly the cfbot is showing a patch conflict again. It's just a trivial > conflict in the regression test schedule so I'm not going to update > the status but it would be good to rebase it so we continue to get > cfbot testing. Done. No changes.
Commits
-
Perform apply of large transactions by parallel workers.
- 216a784829c2 16.0 cited
-
Enhance pg_log_backend_memory_contexts() for auxiliary processes.
- 790fbda90209 15.0 cited
-
Allow GRANT on pg_log_backend_memory_contexts().
- f0b051e322d5 15.0 cited
-
Move Perl test modules to a better namespace
- b3b4d8e68ae8 15.0 cited
-
Unify PostgresNode's new() and get_new_node() methods
- 201a76183e20 15.0 cited
-
Add backtrace support for error reporting
- 71a8a4f6e365 13.0 cited