1. 01 8月, 2003 17 次提交
  2. 31 7月, 2003 13 次提交
    • B
      Modify: · 1c6eba44
      Bruce Momjian 提交于
      > * Implement dirty reads or shared row locks and use them in RI triggers
      1c6eba44
    • B
      Modify: · 644bf7d0
      Bruce Momjian 提交于
      > * Implement dirty reads or shared locks and use them in RI triggers
      644bf7d0
    • B
      contraints -> constraints · 36f3a3c4
      Bruce Momjian 提交于
      Rod Taylor
      36f3a3c4
    • B
      Update Turkish FAQ, Devrim GUNDUZ · 6b8f6a65
      Bruce Momjian 提交于
      6b8f6a65
    • B
      Add fflush of stdout when outputing query. · f766b376
      Bruce Momjian 提交于
      f766b376
    • B
      dbf2pg - Insert xBase-style .dbf-files into a PostgreSQL-table · 82bade79
      Bruce Momjian 提交于
        There is an option "-s oldname=newname", which changes the old field name of
        the dbf-file to the newname in PostgeSQL. If the length of the new name is 0,
        the field is skiped. If you want to skip the first field of the dbf-file,
        you get the wildest error-messages from the backend.
        dbf2pg load the dbf-file via "COPY tablename FROM STDIN". If you skip the
        first field, it is an \t to much in STDIN.
      
      A fix could be an counter j=0, which increments only, if a field is imported
      (IF (strlen(fields[h].db_name)> 0) j++. And only if j > 1 (if an other field is
      imported) the \t is printed.
      
      An other small bug in the README:
      -s start
                    Specify  the  first record-number in the xBase-file
                    we will insert.
      should be
      -e start
                    Specify  the  first record-number in the xBase-file
                    we will insert.
      
      Thomas Behr
      82bade79
    • T
      Add pretty-printing variants of pg_get_viewdef and related functions. · 52347b66
      Tom Lane 提交于
      Patch from Andreas Pflug.
      52347b66
    • B
      Add:; · 12911ea2
      Bruce Momjian 提交于
      > * Allow server log information to be output as INSERT statements
      12911ea2
    • T
      Fix numeric_smaller, numeric_larger, float4smaller, float4larger, · 4b1c6695
      Tom Lane 提交于
      float8smaller, float8larger (and thereby the MIN/MAX aggregates on these
      datatypes) to agree with the datatypes' comparison operations as
      regards NaN handling.  In all these datatypes, NaN is arbitrarily
      considered larger than any normal value ... but MIN/MAX had not gotten
      the word.  Per recent discussion on pgsql-sql.
      4b1c6695
    • B
      Modify: · 0159f7f2
      Bruce Momjian 提交于
      > * Allow log lines to include session-level information, like database and user
      0159f7f2
    • T
      Cause ARRAY[] construct to return a NULL array, rather than raising an · 9ca5c754
      Tom Lane 提交于
      error, if any input element is NULL.  This is not what we ultimately want,
      but until arrays can have NULL elements, it will have to do.  Patch from
      Joe Conway.
      9ca5c754
    • B
      Add: · 082df47b
      Bruce Momjian 提交于
      > * Add database name and user name to logging options
      082df47b
    • T
      When shutting down the regression test postmaster after 'make check', · 5c7d04d2
      Tom Lane 提交于
      wait for the postmaster to actually exit.  Otherwise running repeated
      'make check's tends to misbehave, because we try to remove and recreate
      the data directory while the old PM is still alive.
      5c7d04d2
  3. 30 7月, 2003 2 次提交
    • T
      Fix longstanding error in _bt_search(): should moveright at top of loop not · 892a51c3
      Tom Lane 提交于
      bottom.  Otherwise we fail to moveright when the root page was split while
      we were "in flight" to it.  This is not a significant problem when the root
      is above the leaf level, but if the root was also a leaf (ie, a single-page
      index just got split) we may return the wrong leaf page to the caller,
      resulting in failure to find a key that is in fact present.  Bug has existed
      at least since 7.1, probably forever.
      892a51c3
    • T
      Coerce unknown-literal-constant default values to the column type during · 5e3c09a1
      Tom Lane 提交于
      CREATE TABLE (or ALTER TABLE SET DEFAULT), rather than postponing it to
      the time that the default is inserted into an INSERT command by the
      rewriter.  This reverses an old decision that was intended to make the
      world safe for writing
      	f1 timestamp default 'now'
      but in fact merely made the failure modes subtle rather than obvious.
      Per recent trouble report and followup discussion.
      
      initdb forced since there is a chance that stored default expressions
      will change.
      5e3c09a1
  4. 29 7月, 2003 6 次提交
  5. 28 7月, 2003 2 次提交