Re: Hash table scans outside transactions

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Aidar Imamov <a(dot)imamov(at)postgrespro(dot)ru>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Hash table scans outside transactions
Date: 2025-05-25 11:36:49
Message-ID: CAFiTN-vmfWkuOO=tc_1vCihXHbscMdm_7Ktshu-GTJ-aHEzn5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 21, 2025 at 3:02 AM Aidar Imamov <a(dot)imamov(at)postgrespro(dot)ru> wrote:
>
> Hi!
> I tried to resend this thread directly to myself, but for some reason it
> ended up in the whole hackers list..
>
> I thought I'd chime in on this topic since it hasn't really been
> discussed
> anywhere else (or maybe I missed it).
> I've attached two patches: the first one is a little test extension to
> demonstrate the problem (just add "hash_test" to
> "shared_preload_libraries"),
> and the second is a possible solution. Basically, the idea is that we
> don't
> reset the scan counter if we find scans that started outside of the
> current
> transaction at the end. I have to admit, though, that I can't
> immediately
> say what other implications this might have or what else we need to
> watch
> out for if we try this.
> Maybe any thoughts on that?

I haven't reviewed the complete patch or tested it, but I don't see
any issues with it.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2025-05-25 12:05:59 Re: MERGE issues around inheritance
Previous Message Tender Wang 2025-05-25 11:17:38 Re: MERGE issues around inheritance