1. 02 7月, 2005 8 次提交
    • T
      Avoid function name conflict when plpgsql and rangefuncs regression tests · 975368e2
      Tom Lane 提交于
      execute in parallel.  Spotted by Peter.
      975368e2
    • T
      e6a8eba3
    • T
      Migrate rtree_gist functionality into the core system, and add some · e7e16942
      Tom Lane 提交于
      basic regression tests for GiST to the standard regression tests.
      I took the opportunity to add an rtree-equivalent gist opclass for
      circles; the contrib version only covered boxes and polygons, but
      indexing circles is very handy for distance searches.
      e7e16942
    • P
      875efad4
    • B
      Clarify code to double \\ and '. · 2f7d369a
      Bruce Momjian 提交于
      2f7d369a
    • B
      Clarify: · f009248a
      Bruce Momjian 提交于
      < 	o Replace crude DELETE FROM method of pg_dumpall for cleaning of
      < 	  roles with separate DROP commands
      > 	o Replace crude DELETE FROM method of pg_dumpall --clean for
      >           cleaning of roles with separate DROP commands
      f009248a
    • B
      Update for roles: · fee590c8
      Bruce Momjian 提交于
      < * Allow limits on per-db/user connections
      > * Allow limits on per-db/role connections
      < * Prevent default re-use of sysids for dropped users and roles
      <
      <   Currently, if a user is removed while he still owns objects, a new
      <   user given might be given their user id and inherit the
      <   previous users objects.
      <
      450c444
      < * Add COMMENT ON for all cluster global objects (users, roles, databases
      > * Add COMMENT ON for all cluster global objects (roles, databases
      609c603
      < 	  users and roles with separate DROP commands
      > 	  roles with separate DROP commands
      fee590c8
    • B
      Update for roles: · b00f557d
      Bruce Momjian 提交于
      < * Prevent default re-use of sysids for dropped users and groups
      > * Prevent default re-use of sysids for dropped users and roles
      450c450
      < * Add COMMENT ON for all cluster global objects (users, groups, databases
      > * Add COMMENT ON for all cluster global objects (users, roles, databases
      609c609
      < 	  users and groups with separate DROP commands
      > 	  users and roles with separate DROP commands
      b00f557d
  2. 01 7月, 2005 8 次提交
  3. 30 6月, 2005 10 次提交
  4. 29 6月, 2005 7 次提交
  5. 28 6月, 2005 4 次提交
  6. 27 6月, 2005 3 次提交
    • T
      Concurrency for GiST · e8cab5fe
      Teodor Sigaev 提交于
      - 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
                        simultaneously
                      - 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
      e8cab5fe
    • T
      Modify pg_dump to assume that a check constraint is inherited if its · c3be085a
      Tom Lane 提交于
      name matches the name of any parent-table constraint, without looking
      at the constraint text.  This is a not-very-bulletproof workaround for
      the problem exhibited by Berend Tober last month.  We really ought to
      record constraint inheritance status in pg_constraint, but it's looking
      like that may not get done for 8.1 --- and even if it does, we will
      need this kluge for dumping from older servers.
      c3be085a
    • B
      Done: · fc722403
      Bruce Momjian 提交于
      > * -Remove kerberos4 from source tree
      fc722403