From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, ma lz <ma100(at)hotmail(dot)com> |
Subject: | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
Date: | 2025-03-22 10:12:58 |
Message-ID: | Z96NKlt-uNnICyhs@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Re: To Michael Paquier
> > >> +#define JUMBLE_CUSTOM(nodetype, item) \
> > >> + _jumble##nodetype##_##item(jstate, expr, expr->item)
> >
> > In this one, I want to mean that we require a custom per-field
> > function to look like that:
> > _jumbleNodefoo_field(JumbleState *jstate, NodeFoo *expr, FieldType field);
>
> Perhaps this:
Or actually more explicit:
/*
* Per-field custom jumble functions have this signature:
* _jumbleNodefoo_field(JumbleState *jstate, NodeFoo *expr, FieldType field);
*/
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-03-22 10:32:47 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
Previous Message | Christoph Berg | 2025-03-22 09:43:00 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |
From | Date | Subject | |
---|---|---|---|
Next Message | Antonin Houska | 2025-03-22 10:14:14 | Re: why there is not VACUUM FULL CONCURRENTLY? |
Previous Message | Antonin Houska | 2025-03-22 09:43:29 | Re: why there is not VACUUM FULL CONCURRENTLY? |