Horton

Re: post-freeze damage control

Alena Rybakina <lena.ribackina@yandex.ru>

View thread
From: Alena Rybakina <lena.ribackina@yandex.ru>
To: Andrei Lepikhov <a.lepikhov@postgrespro.ru>
Cc: Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2024-06-18T10:05:23Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. revert: Transform OR clauses to ANY expression

  2. Fix incorrect calculation in BlockRefTableEntryGetBlocks.

Hi! Unfortunately,Iwas notableto fullyunderstandyourmessage.Couldyou 
explainit to meplease?

On 09.04.2024 16:20, Andrei Lepikhov wrote:
>
> Moreover, it helps even SeqScan: attempting to find a value in the 
> hashed array is much faster than cycling a long-expression on each 
> incoming tuple.

AsIunderstandit,youtalkedaboutspeedingupSeqScan 
byfasterre-searchingthroughthe useof a hashtable. Atthe same time, 
wehaveto builditbeforethat,whenthere was the initiallookuptuples,right?

Ifoundthisinformationinthe ExecEvalHashedScalarArrayOp 
function,andIassumeyoumeantthisfunctioninyourmessage.

But I couldn't find information, when you told about cycling a 
long-expression on each incoming tuple. Could you ask me what function 
you were talking about or maybe functionality? I saw ExecSeqScan 
function, but I didn't see it.

-- 
Regards,
Alena Rybakina
Postgres Professional:http://www.postgrespro.com
The Russian Postgres Company