| From: | Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal to have INCLUDE/EXCLUDE options for altering option values |
| Date: | 2024-08-27 17:47:00 |
| Message-ID: | CACX+KaMhGn=UQhwqyO3oGf_UC0HtfrESyA7ZX=zOr37vi=v5yQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I'm not convinced
> that this problem would arise often enough in practice that it's worth
> adding a feature to address it. A user who has this problem can pretty
> easily do some scripting to address it
> AFAICS this proposal also represents a tiny use case.
Thanks Robert and Euler for the feedback.
Ack, Initially while working on the solution I thought this can be a common
problem. But I agree if the use case is small we can postpone supporting
such syntax for the future.
I can then withdraw the patch.
Regards
Ayush Vatsa
AWS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-08-27 18:13:54 | Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) |
| Previous Message | Robert Haas | 2024-08-27 17:45:08 | Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) |