| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Subject: | Re: Add pg_get_injection_points() for information of injection points |
| Date: | 2025-04-14 23:00:50 |
| Message-ID: | Z_2TosE09s-dErbm@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 14, 2025 at 04:29:37PM +0300, Aleksander Alekseev wrote:
> If I didn't miss anything, all SQL functions dealing with injection
> points are gathered in injection_points extension so IMO
> pg_get_injection_points() belongs there. It would be awkward to have
> it in the core considering the fact that injection points presumably
> should be disabled in release builds.
There are two more in test_aio, and by design out-of-core extensions
can define their own.
> Users will see a function in \df that does nothing.
Yeah, this one's true if --enable-injection-points is not used.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilia Evdokimov | 2025-04-14 23:14:37 | Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment |
| Previous Message | Mahendra Singh Thalor | 2025-04-14 22:55:42 | Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore |