Re: Faster "SET search_path" - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Faster "SET search_path"
Date
Msg-id 52d12be414288cc6bc95d0f1017156a68b66a653.camel@j-davis.com
Whole thread Raw
In response to Re: Faster "SET search_path"  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Mon, 2023-11-20 at 17:13 -0800, Jeff Davis wrote:
> Will commit 0005 soon.

Committed.

> I also attached a trivial 0006 patch that uses SH_STORE_HASH. I
> wasn't
> able to show much benefit, though, even when there's a bucket
> collision. Perhaps there just aren't enough elements to matter -- I
> suppose there would be a benefit if there are lots of unique
> search_path strings, but that doesn't seem very plausible to me. If
> someone thinks it's worth committing, then I will, but I don't see
> any
> real upside or downside.

I tried again by forcing a hash table with ~25 entries and 13
collisions, and even then, SH_STORE_HASH didn't make a difference in my
test. Maybe a microbenchmark would show a difference, but I didn't see
much reason to commit 0006. (There's also no downside, so I was tempted
to commit it just so I wouldn't have to put more thought into whether
it's a problem or not.)

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Built-in CTYPE provider
Next
From: John Naylor
Date:
Subject: Re: Change GUC hashtable to use simplehash?