From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Greg Stark <stark(at)mit(dot)edu>, torikoshia(at)oss(dot)nttdata(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Printing backtrace of postgres processes |
Date: | 2023-11-04 20:19:00 |
Message-ID: | CALj2ACW34HuRUvS3bR_cEKgmueQVkOPzU8h8xBpOS9EMqajQ5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 20, 2023 at 8:22 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 11 Jan 2023, at 15:44, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> >
> > On Wed, Nov 30, 2022 at 11:43 AM Bharath Rupireddy
> > <bharath(dot)rupireddyforpostgres(at)gmail(dot)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 | Content-Type | Size |
---|---|---|
v24-0001-Move-sending-multiplexed-SIGUSR1-signal-code-to-.patch | application/x-patch | 5.6 KB |
v24-0002-Add-function-to-log-the-backtrace-of-specified-p.patch | application/x-patch | 24.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2023-11-04 20:57:48 | Re: Inconsistent use of "volatile" when accessing shared memory? |
Previous Message | Andrey M. Borodin | 2023-11-04 20:07:52 | Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock |