Request a Demo
Home   >   mailing lists

pgsql: Preventing intersection of ranges during page split. - Mailing list pgsql-committers

From [email protected] (Teodor Sigaev)
Subject pgsql: Preventing intersection of ranges during page split.
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Tree view 
Log Message:
-----------
Preventing intersection of ranges during page split. Changes are only
optimization, so don't backpatch.

Modified Files:
--------------
    pgsql/contrib/btree_gist:
        btree_cash.c (r1.9 -> r1.10)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_cash.c?r1=1.9&r2=1.10)
        btree_date.c (r1.7 -> r1.8)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_date.c?r1=1.7&r2=1.8)
        btree_float4.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_float4.c?r1=1.8&r2=1.9)
        btree_float8.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_float8.c?r1=1.8&r2=1.9)
        btree_inet.c (r1.10 -> r1.11)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_inet.c?r1=1.10&r2=1.11)
        btree_int2.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_int2.c?r1=1.8&r2=1.9)
        btree_int4.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_int4.c?r1=1.8&r2=1.9)
        btree_int8.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_int8.c?r1=1.8&r2=1.9)
        btree_interval.c (r1.12 -> r1.13)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_interval.c?r1=1.12&r2=1.13)
        btree_macaddr.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_macaddr.c?r1=1.8&r2=1.9)
        btree_oid.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_oid.c?r1=1.8&r2=1.9)
        btree_time.c (r1.16 -> r1.17)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_time.c?r1=1.16&r2=1.17)
        btree_ts.c (r1.17 -> r1.18)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_ts.c?r1=1.17&r2=1.18)
        btree_utils_var.c (r1.21 -> r1.22)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_utils_var.c?r1=1.21&r2=1.22)

pgsql-committers by date:

Previous
From: [email protected] (Tom Lane)
Date:
Subject: pgsql: Mark application_name as GUC_REPORT so that the value will be
Next
From: [email protected] (Bruce Momjian)
Date:
Subject: pgsql: thread-safety Apply full patch to enable thread-safety by