From: | Xing Guo <higuoxing(at)gmail(dot)com> |
---|---|
To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [RFC] Clang plugin for catching suspicious typedef casting |
Date: | 2023-08-15 02:21:44 |
Message-ID: | CACpMh+B=LZ3C7Pw3o7Mj_0cyEP5Z-+o7n33NrNDnR4qMVOrGow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 8/10/23, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
>> On Wed, Aug 09, 2023 at 03:23:32PM +0200, Peter Eisentraut wrote:
>> On 03.08.23 18:56, Dmitry Dolgov wrote:
>> > I would like to get your opinion, folks. Does it sound interesting
>> > enough for the community, is it worth it to pursue the idea?
>>
>> I think it's interesting, and doesn't look too invasive.
+1.
>> Maybe we can come up with three or four interesting use cases and try to
>> implement them. BlockNumber vs. Buffer type checking is obviously a bit
>> marginal to get anyone super-excited, but it's a reasonable demo.
Several months ago, I implemented a clang plugin[1] for checking
suspicious return/goto/break/continue in PG_TRY/PG_CATCH blocks and it
found unsafe codes in Postgres[2]. It's implemented using clang's AST
matcher API.
I would like to contribute it well if this RFC can be accepted.
[1] https://github.com/higuoxing/clang-plugins/blob/main/lib/ReturnInPgTryBlockChecker.cpp
[2] https://www.postgresql.org/message-id/flat/CACpMh%2BCMsGMRKFzFMm3bYTzQmMU5nfEEoEDU2apJcc4hid36AQ%40mail.gmail.com
--
Best Regards,
Xing
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2023-08-15 02:33:38 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
Previous Message | Masahiko Sawada | 2023-08-15 02:21:15 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |