On 5/25/25 13:36, Dilip Kumar wrote:
> On Wed, May 21, 2025 at 3:02 AM Aidar Imamov 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
>> discuss
On Wed, May 21, 2025 at 3:02 AM Aidar Imamov 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
Aidar Imamov wrote 2025-05-21 00:32:
Ashutosh Bapat wrote 2023-03-28 15:58:
Bumping it to attract some attention.
On Tue, Mar 21, 2023 at 12:51 PM Ashutosh Bapat
wrote:
Hi,
Hash table scans (seq_scan_table/level) are cleaned up at the end of
a
transaction in AtEOXact_HashTables(). If a has
Ashutosh Bapat wrote 2023-03-28 15:58:
Bumping it to attract some attention.
On Tue, Mar 21, 2023 at 12:51 PM Ashutosh Bapat
wrote:
Hi,
Hash table scans (seq_scan_table/level) are cleaned up at the end of a
transaction in AtEOXact_HashTables(). If a hash seq scan continues
beyond transaction
Bumping it to attract some attention.
On Tue, Mar 21, 2023 at 12:51 PM Ashutosh Bapat
wrote:
>
> Hi,
> Hash table scans (seq_scan_table/level) are cleaned up at the end of a
> transaction in AtEOXact_HashTables(). If a hash seq scan continues
> beyond transaction end it will meet "ERROR: no hash_
Hi,
Hash table scans (seq_scan_table/level) are cleaned up at the end of a
transaction in AtEOXact_HashTables(). If a hash seq scan continues
beyond transaction end it will meet "ERROR: no hash_seq_search scan
for hash table" in deregister_seq_scan(). That seems like a limiting
the hash table usage
