Re: post-freeze damage control

From: Alena Rybakina <lena(dot)ribackina(at)yandex(dot)ru>
To: Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: post-freeze damage control
Date: 2024-06-18 10:05:23
Message-ID: 9df73f5d-9b81-4350-8db4-4663ab637533@yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Frédéric Yhuel 2024-06-18 10:36:42 Re: New GUC autovacuum_max_threshold ?
Previous Message shveta malik 2024-06-18 09:58:51 Re: Conflict Detection and Resolution