Postgres Pro
Downloads
Home   >   mailing lists

Re: Printing backtrace of postgres processes - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Printing backtrace of postgres processes
Date
Msg-id CALj2ACW34HuRUvS3bR_cEKgmueQVkOPzU8h8xBpOS9EMqajQ5w@mail.gmail.com
Whole thread Raw
In response to Re: Printing backtrace of postgres processes  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Printing backtrace of postgres processes  (Maciek Sakrejda <m.sakrejda@gmail.com>)
Re: Printing backtrace of postgres processes  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
Tree view 
On Thu, Jul 20, 2023 at 8:22 PM Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 11 Jan 2023, at 15:44, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote:
> >
> > On Wed, Nov 30, 2022 at 11:43 AM Bharath Rupireddy
> > <bharath.rupireddyforpostgres@gmail.com> wrote:
> >>
> >> I'm attaching the v22 patch set for further review.
> >
> > Needed a rebase due to 216a784829c2c5f03ab0c43e009126cbb819e9b2.
> > Attaching v23 patch set for further review.
>
> This thread has stalled for well over 6 months with the patch going from CF to
> CF.  From skimming the thread it seems that a lot of the details have been
> ironed out with most (all?) objections addressed.  Is any committer interested
> in picking this up?  If not we should probably mark it returned with feedback.

Rebase needed due to function oid clash. Picked the new OID with the
help of src/include/catalog/unused_oids. PSA v24 patch set.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachment

pgsql-hackers by date:

Previous
From: "Andrey M. Borodin"
Date:
Subject: Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock
Next
From: Jeff Davis
Date:
Subject: Re: Inconsistent use of "volatile" when accessing shared memory?