1. 25 6月, 2003 18 次提交
    • B
      client-auth.sgml references a renamed ID in runtime.sgml · 503a88a6
      Bruce Momjian 提交于
      Josh Berkus
      503a88a6
    • B
      Attached is the fully corrected version of the re-ording patch for · 2a5e0bb6
      Bruce Momjian 提交于
      Runtime.sgml and dependant files.
      
      Josh Berkus
      2a5e0bb6
    • B
      - Corrections for tables, columns with uppercase characters · 51d16423
      Bruce Momjian 提交于
      - Don't attempt to convert partial or expressional unique indexes
      - Don't attempt to convert unique indexes based on a non-default
      opclasses
      
      - Untested prevention of conversion of non-btree indexes unique
      indexes.  Untested as postgresql doesn't allow hash, gist, or rtree
      based indexes to be unique.
      
      rbt=# create unique index t on a using hash (col);
      ERROR:  DefineIndex: access method "hash" does not support UNIQUE
      indexes
      rbt=# create unique index t on a using gist (col);
      ERROR:  DefineIndex: access method "gist" does not support UNIQUE
      indexes
      rbt=# select version();
                                      version
      ------------------------------------------------------------------------
       PostgreSQL 7.4devel on i386-unknown-freebsd4.8, compiled by GCC 2.95.4
      
      Rod Taylor
      51d16423
    • B
      Please apply attached patch to contrib/dblink. It adds named persistent · 8f337e86
      Bruce Momjian 提交于
      connections to dblink.
      
      Shridhar Daithanka
      8f337e86
    • B
      · 92798de0
      Bruce Momjian 提交于
      This is a bug in python interface module,
      postgresql-7.3.3/src/interfaces/python/pg.py.
      
      _quote() function fails due to integer overflow if input d is larger
      than max integer.
      
      In the case where the column type is "BIGINT", the input d may very well
      be larger than max integer while its type, t, is labeled 'int'.
      The conversion on line 19, return "%d" % int(d), will fail due to
      "OverflowError: long int too large to convert to int".
      
      
      
      Please describe a way to repeat the problem.   Please try to provide a
      concise reproducible example, if at all possible:
      ----------------------------------------------------------------------
      
      [1] create a table with a column type 'BIGINT'.
      [2] use pg.DB.insert() to insert a value that is larger than max integer
      
      If you know how this problem might be fixed, list the solution below:
      ---------------------------------------------------------------------
      
      Just changing the conversion at line 19 of pg.py to long(d) instead of
      int(d) should fix it. The following is a patch:
      
      Chih-Hao Huang
      92798de0
    • B
      >> If a transaction marks a tuple for update and later commits without · dd23a882
      Bruce Momjian 提交于
      >> actually having updated the tuple, [...] can we simply
      >> set the HEAP_XMAX_INVALID hint bit of the tuple?
      >
      >AFAICS this is a reasonable thing to do.
      
      Thanks for the confirmation.  Here's a patch which also contains some
      more noncritical changes to tqual.c:
       .  make code more readable by introducing local variables for xvac
       .  no longer two separate branches for aborted and crashed.
          The actions were the same in all cases.
      
      Manfred Koizar
      dd23a882
    • B
      Most of the synopsis areas for DROP commands use "name" as the · fce529e1
      Bruce Momjian 提交于
      identifier, while some areas do not.
      
      The attached converts be below to "name":
      conversion_name
      index_name
      
      
      The below have an existing, initdb supplied, entity named "name".  As
      such, it could be confusing for the reader to see that identifier used
      in the example.
      
      domainname
      typename
      
      Rod Taylor
      fce529e1
    • B
      Revert ORDBMS change, per Peter. · 7eac8e38
      Bruce Momjian 提交于
      7eac8e38
    • B
      Alter query.sgml to mention PostgreSQL as an ORDBMS. This falls in line · db57396c
      Bruce Momjian 提交于
      with advocacy and 'portal' websites.
      
      Link to createdb / dropdb from the tutorial page about create / dropdb.
      A pair of notes were asking about more info...
      
      Rod Taylor
      db57396c
    • B
      In an attempt to simplify my life I'm submitting this patch that · 7f791925
      Bruce Momjian 提交于
      restructures the deferred trigger queue.  The fundamental change is to
      put all the static variables to hold the deferred triggers in a single
      structure.
      
      Alvaro Herrera
      7f791925
    • B
      Add x86_64 support for spinlocks. · aa62f7f7
      Bruce Momjian 提交于
      Jeffrey W. Baker
      aa62f7f7
    • B
      Small patch to link to the proper place in the "runtime" file, · 7cb4278e
      Bruce Momjian 提交于
      and to add the "schemaname" column to the description of the
      pg_stats view.
      
      Greg Sabino Mullane
      7cb4278e
    • B
      Array mega-patch. · 46bf6514
      Bruce Momjian 提交于
      Joe Conway
      46bf6514
    • B
      Done: · 50e53236
      Bruce Momjian 提交于
      > * -Add IPv6 capability to INET/CIDR types
      50e53236
    • B
      Jim C. Nasby wrote: · 7b1f6ffa
      Bruce Momjian 提交于
      > Second argument to metaphone is suposed to set the limit on the
      > number of characters to return, but it breaks on some phrases:
      >
      > usps=# select metaphone(a,3),metaphone(a,4),metaphone(a,20) from
      > (select 'Hello world'::varchar AS a) a;
      > HLW       | HLWR      | HLWRLT
      >
      > usps=# select metaphone(a,3),metaphone(a,4),metaphone(a,20) from
      > (select 'A A COMEAUX MEMORIAL'::varchar AS a) a;
        > AKM       | AKMKS     | AKMKSMMRL
      >
      > In every case I've found that does this, the 4th and 5th letters are
      > always 'KS'.
      
      Nice catch.
      
      There was a bug in the original metaphone algorithm from CPAN. Patch
      attached (while I was at it I updated my email address, changed the
      copyright to PGDG, and removed an unnecessary palloc). Here's how it
      looks now:
      
      regression=# select metaphone(a,4) from (select 'A A COMEAUX
      MEMORIAL'::varchar AS a) a;
         metaphone
      -----------
         AKMK
      (1 row)
      
      regression=# select metaphone(a,5) from (select 'A A COMEAUX
      MEMORIAL'::varchar AS a) a;
         metaphone
      -----------
         AKMKS
      (1 row)
      
      Joe Conway
      7b1f6ffa
    • B
      4b1fe231
    • B
      Add ipv6 address parsing support to 'inet' and 'cidr' data types. · 945543d9
      Bruce Momjian 提交于
              Regression tests for IPv6 operations added.
      
              Documentation updated to document IPv6 bits.
      
              Stop treating IPv4 as an "unsigned int" and IPv6 as an array of
              characters.  Instead, always use the array of characters so we
              can have one function fits all.  This makes bitncmp(), addressOK(),
              and several other functions "just work" on both address families.
      
              add family() function which returns integer 4 or 6 for IPv4 or
              IPv6.  (See examples below)  Note that to add this new function
              you will need to dump/initdb/reload or find the correct magic
              to add the function to the postgresql function catalogs.
      
              IPv4 addresses always sort before IPv6.
      
              On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses.
              This prevents the need for a dump and reload, but lets IPv6 parsing
              work on machines without AF_INET6.
      
              To select all IPv4 addresses from a table:
      
                      select * from foo where family(addr) = 4 ...
      
              Order by and other bits should all work.
      
      Michael Graff
      945543d9
    • B
      Update: · 4dab978c
      Bruce Momjian 提交于
      < * Have SELECT '13 minutes'::interval display zero seconds
      > * Have SELECT '13 minutes'::interval display zero seconds in ISO datestyle
      4dab978c
  2. 24 6月, 2003 17 次提交
  3. 23 6月, 2003 5 次提交
    • B
      Add: · 5b106845
      Bruce Momjian 提交于
      > * Exit postmaster if postgresql.conf can not be opened
      5b106845
    • B
      Add: · 52001f61
      Bruce Momjian 提交于
      	* Allow SSL-enabled clients to turn off SSL transfers
      52001f61
    • B
      Add: · ec5020f0
      Bruce Momjian 提交于
      > * Change CVS $Id$ to $PostgreSQL$
      ec5020f0
    • T
      Revise hash join and hash aggregation code to use the same datatype- · bff0422b
      Tom Lane 提交于
      specific hash functions used by hash indexes, rather than the old
      not-datatype-aware ComputeHashFunc routine.  This makes it safe to do
      hash joining on several datatypes that previously couldn't use hashing.
      The sets of datatypes that are hash indexable and hash joinable are now
      exactly the same, whereas before each had some that weren't in the other.
      bff0422b
    • T
      Fix some index entries. · 0dda75f6
      Tom Lane 提交于
      0dda75f6