pgsql: Tweak dynahash.c to not allocate so many entries at once when - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Tweak dynahash.c to not allocate so many entries at once when
Date
Msg-id 20050626233234.D5CB752823@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Tweak dynahash.c to not allocate so many entries at once when dealing
with a table that has a small predicted size.  Avoids wasting several
hundred K on the timezone hash table, which is likely to have only one
or a few entries, but the entries use up 10Kb apiece ...

Modified Files:
--------------
    pgsql/src/backend/utils/hash:
        dynahash.c (r1.62 -> r1.63)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/hash/dynahash.c.diff?r1=1.62&r2=1.63)
    pgsql/src/include/utils:
        hsearch.h (r1.38 -> r1.39)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/hsearch.h.diff?r1=1.38&r2=1.39)
    pgsql/src/timezone:
        pgtz.c (r1.35 -> r1.36)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/pgtz.c.diff?r1=1.35&r2=1.36)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add Oracle-compatible GREATEST and LEAST functions.
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Adjust contrib/seg &< and &> operators so that r-tree indexing