Downloads
Home   >   mailing lists

Re: Some ExecSeqScan optimizations - Mailing list pgsql-hackers

From Nikita Malakhov
Subject Re: Some ExecSeqScan optimizations
Date
Msg-id CAN-LCVMMXqLj=j8Edqd99E9Pe1ayhWc8KyotfUfxv9-qV6ziqg@mail.gmail.com
Whole thread Raw
In response to Re: Some ExecSeqScan optimizations  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Some ExecSeqScan optimizations
List pgsql-hackers
Tree view
Hi Amit!

It's a pity I missed this thread when you developed the patch.
I've developed a feature recently and discovered that SeqScan
does not make use of scan keys, and there is a Tom Lane's
comment regarding this:
  * Note that unlike IndexScan, SeqScan never use keys in heap_beginscan
  * (and this is very bad) - so, here we do not check are keys ok or not.

Have you considered passing scan keys like it is done in IndexScan?

Thanks!

--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: Explicitly enable meson features in CI
Next
From: Dilip Kumar
Date:
Subject: Re: Proposal: Global Index for PostgreSQL