Skip site navigation (1) Skip section navigation (2)

pgsql: Concurrency for GiST - full concurrency for

From: teodor(at)svr1(dot)postgresql(dot)org (Teodor Sigaev)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Concurrency for GiST - full concurrency for
Date: 2005-06-27 12:45:23
Message-ID: (view raw or whole thread)
Lists: pgsql-committers
Log Message:
Concurrency for GiST
- full concurrency for insert/update/select/vacuum:
        - select and vacuum never locks more than one page simultaneously
        - select (gettuple) hasn't any lock across it's calls
        - insert never locks more than two page simultaneously:
                - during search of leaf to insert it locks only one page
                - while walk upward to the root it locked only parent (may be
                  non-direct parent) and child. One of them X-lock, another may
                  be S- or X-lock
- 'vacuum full' locks index
- improve gistgetmulti
- simplify XLOG records

Fix bug in index_beginscan_internal: LockRelation may clean
  rd_aminfo structure, so move GET_REL_PROCEDURE after LockRelation

Modified Files:
        gist.c (r1.121 -> r1.122)
        gistget.c (r1.49 -> r1.50)
        gistscan.c (r1.58 -> r1.59)
        gistutil.c (r1.2 -> r1.3)
        gistvacuum.c (r1.2 -> r1.3)
        gistxlog.c (r1.3 -> r1.4)
        indexam.c (r1.83 -> r1.84)
        gist.h (r1.47 -> r1.48)
        gist_private.h (r1.5 -> r1.6)
        gistscan.h (r1.26 -> r1.27)
        catversion.h (r1.281 -> r1.282)
        pg_am.h (r1.36 -> r1.37)

pgsql-committers by date

Next:From: User AndreasDate: 2005-06-27 22:12:41
Subject: tablelog - tablelog: fix an error (wrong parameter was printed)
Previous:From: User ApplejackDate: 2005-06-27 05:53:25
Subject: uri - uri: Changed to not install in pg_catalog.

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group