| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: making EXPLAIN extensible |
| Date: | 2025-03-05 17:20:22 |
| Message-ID: | 82f96eed213c8d76b36b8a3f504576e5af493270.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2025-03-04 at 16:23 -0500, Robert Haas wrote:
> But, I'm doubtful that
> letting unrelated extensions try to share the same option name is
> that
> thing.
This sub-discussion started because we were wondering whether to prefix
the options. I'm just pointing out that, even if there is a collision,
and it happened to work, it's as likely to be a feature as a bug.
I didn't look into the technical details to see what might be required
to allow that kind of collaboration, and I am not suggesting you
redesign the entire feature around that idea.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Burd, Greg | 2025-03-05 17:20:34 | Re: Expanding HOT updates for expression and partial indexes |
| Previous Message | Andres Freund | 2025-03-05 17:16:20 | Re: Should we add debug_parallel_query=regress to CI? |