Re: POC: Extension for adding distributed tracing - pg_tracing - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: POC: Extension for adding distributed tracing - pg_tracing
Date
Msg-id CAJ7c6TPjTxTgqL1zYGjbU1Mwfx1zB3GqZghjNWa+GVtJ028giA@mail.gmail.com
Whole thread Raw
In response to Re: POC: Extension for adding distributed tracing - pg_tracing  (Craig Ringer <craig.ringer@enterprisedb.com>)
Responses Re: POC: Extension for adding distributed tracing - pg_tracing
List pgsql-hackers
Hi Anthonin,

> [...]
>
> The usual approach is to have pre-allocated memory. This must actually be written (zeroed usually) or it might be
lazilyallocated only on page fault. And it can't be copy on write memory allocated once in postmaster startup then
inheritedby fork.
 
>
> That imposes an overhead for every single postgres backend. So maybe there's a better solution.

It looks like the patch rotted a bit, see cfbot. Could you please
submit an updated version?

Best regards,
Aleksander Alekseev (wearing co-CFM hat)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Weird test mixup
Next
From: Tom Lane
Date:
Subject: Re: Support json_errdetail in FRONTEND builds