Postgres Pro
Downloads
Home   >   mailing lists

Small optimization set tuple block/tableOid once - Mailing list pgsql-hackers

From Ranier Vilela
Subject Small optimization set tuple block/tableOid once
Date
Msg-id CAEudQAqc8TYoHXGgUcnTJm-nc2TF2WwORm8rh1=nLjMVj1UkbQ@mail.gmail.com
Whole thread Raw
Responses Re: Small optimization set tuple block/tableOid once
List pgsql-hackers
Tree view
Hi.

Inspired by [1]
There is an opportunity for optimization according to the commit:
" Due to splitting the block id into two 16 bit integers, BlockIdSet() is more expensive than one might think. Doing it once per returned tuple shows up as a small but reliably reproducible cost. It's simple enough to set the block number just once per block in pagemode, so do so."

By moving the invariants out of the loop, it really is an improvement.

Then the following sources can be optimized:
contrib/pg_visibility/pg_visibility.c
contrib/pgstattuple/pgstatapprox.c
src/backend/access/heap/heapam.c
src/backend/access/heap/heapam_handler.c
src/backend/access/heap/pruneheap.c
src/backend/access/heap/vacuumlazy.c
src/backend/commands/dbcommands.c

Attached all patchs.

best regards,
Ranier Vilela

Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: pg_restore documentation and --create/--single-transaction limitation
Next
From: Mahendra Singh Thalor
Date:
Subject: Re: getting "shell command argument contains a newline or carriage return:" error with pg_dumpall when db name have new line in double quote