Space management for PGresult - Mailing list pgsql-patches

From Atsushi Ogawa
Subject Space management for PGresult
Date
Msg-id 613787150511222321u75c657c5i@mail.gmail.com
Whole thread Raw
Responses Re: Space management for PGresult  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Space management for PGresult  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-patches
In space management for PGresult of libpq, the block size of PGresult
is always PGRESULT_DATA_BLOCKSIZE(2048bytes). Therefore, when a large
result of query is received, malloc is executed many times.

My proposal is to enlarge the size of the block whenever the block is
allocated. The size of first block is PGRESULT_DATA_BLOCKSIZE. And the
size of the following blocks will be doubled until it reaches
PGRESULT_MAX_DATA_BLOCKSIZE.

PGRESULT_MAX_DATA_BLOCKSIZE is new constants. I think that 2Mbytes is
good enough for this constants.

The test result is the following:

Test SQL:
select * from accounts; (It is pgbench's table. scale factor is 10.)

The number of malloc calls at pqResultAlloc:
 8.1.0  : 80542
 patched:    86

Execution time:
 8.1.0  : 6.80 sec
 patched: 6.73 sec

regards,

--- Atsushi Ogawa

Attachment

pgsql-patches by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: TODO Item - Add system view to show free space map
Next
From: Tatsuo Ishii
Date:
Subject: Re: Patch to allow contrib/pgbench files to have blank