| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CREATE FUNCTION ... SEARCH { DEFAULT | SYSTEM | SESSION } |
| Date: | 2023-12-05 00:55:40 |
| Message-ID: | 47d7e3408b4e84c8cd76a6c906e1eba053b1f198.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2023-11-21 at 09:24 -0500, Robert Haas wrote:
> As to the second, could we somehow come
> up with an API for guc.c where you can ask for an opaque handle that
> will later allow you to do a fast-SET of a GUC?
Yes, attached. That provides a significant speedup: my test goes from
around ~7300ms to ~6800ms.
This doesn't seem very controversial or complex, so I'll probably
commit this soon unless someone else has a comment.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Cache-opaque-handle-for-GUC-option-to-avoid-repea.patch | text/x-patch | 7.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2023-12-05 02:43:42 | Re: gai_strerror() is not thread-safe on Windows |
| Previous Message | zhihuifan1213 | 2023-12-05 00:28:21 | Re: Avoid detoast overhead when possible |