| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Faster "SET search_path" |
| Date: | 2023-08-01 05:28:31 |
| Message-ID: | f555c41554c7f5ff2699c085836ea94beac09bad.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2023-07-29 at 12:44 -0400, Isaac Morland wrote:
> Essentially, "just" observe efficiently (somehow) that no change is
> needed, and skip changing it?
I gave this a try and it speeds things up some more.
There might be a surprise factor with an optimization like that,
though. If someone becomes accustomed to the function running fast,
then changing the search_path in the caller could slow things down a
lot and it would be hard for the user to understand what happened.
Also, there are a few implementation complexities because I think we
need to still trigger the same invalidation that happens in
assign_search_path().
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-08-01 05:32:10 | Re: Simplify some logical replication worker type checking |
| Previous Message | Michael Paquier | 2023-08-01 05:03:36 | Re: Incorrect handling of OOM in WAL replay leading to data loss |