1. 06 Sep, 2004 1 commit
  2. 30 Aug, 2004 2 commits
  3. 29 Aug, 2004 2 commits
  4. 28 Aug, 2004 2 commits
  5. 25 Aug, 2004 1 commit
    • Tom Lane's avatar
      Revise ResourceOwner code to avoid accumulating ResourceOwner objects · fe455ee1
      Tom Lane authored
      for every command executed within a transaction.  For long transactions
      this was a significant memory leak.  Instead, we can delete a portal's
      or subtransaction's ResourceOwner immediately, if we physically transfer
      the information about its locks up to the parent owner.  This does not
      fully solve the leak problem; we need to do something about counting
      multiple acquisitions of the same lock in order to fix it.  But it's a
      necessary step along the way.
      fe455ee1
  6. 11 Aug, 2004 1 commit
  7. 03 Aug, 2004 1 commit
  8. 01 Aug, 2004 2 commits
    • Tom Lane's avatar
      Update the in-code documentation about the transaction system. Move it · 410b1dfb
      Tom Lane authored
      into a README file instead of being in xact.c's header comment.
      Alvaro Herrera.
      410b1dfb
    • Tom Lane's avatar
      Some mop-up work for savepoints (nested transactions). Store a small · efcaf1e8
      Tom Lane authored
      number of active subtransaction XIDs in each backend's PGPROC entry,
      and use this to avoid expensive probes into pg_subtrans during
      TransactionIdIsInProgress.  Extend EOXactCallback API to allow add-on
      modules to get control at subxact start/end.  (This is deliberately
      not compatible with the former API, since any uses of that API probably
      need manual review anyway.)  Add basic reference documentation for
      SAVEPOINT and related commands.  Minor other cleanups to check off some
      of the open issues for subtransactions.
      Alvaro Herrera and Tom Lane.
      efcaf1e8
  9. 31 Jul, 2004 1 commit
    • Tom Lane's avatar
      plpgsql does exceptions. · beda4814
      Tom Lane authored
      There are still some things that need refinement; in particular I fear
      that the recognized set of error condition names probably has little in
      common with what Oracle recognizes.  But it's a start.
      beda4814
  10. 28 Jul, 2004 1 commit
    • Tom Lane's avatar
      Fix subtransaction behavior for large objects, temp namespace, files, · 1bf3d615
      Tom Lane authored
      password/group files.  Also allow read-only subtransactions of a read-write
      parent, but not vice versa.  These are the reasonably noncontroversial
      parts of Alvaro's recent mop-up patch, plus further work on large objects
      to minimize use of the TopTransactionResourceOwner.
      1bf3d615
  11. 27 Jul, 2004 1 commit
  12. 17 Jul, 2004 1 commit
    • Tom Lane's avatar
      Invent ResourceOwner mechanism as per my recent proposal, and use it to · fe548629
      Tom Lane authored
      keep track of portal-related resources separately from transaction-related
      resources.  This allows cursors to work in a somewhat sane fashion with
      nested transactions.  For now, cursor behavior is non-subtransactional,
      that is a cursor's state does not roll back if you abort a subtransaction
      that fetched from the cursor.  We might want to change that later.
      fe548629
  13. 01 Jul, 2004 2 commits
  14. 03 Jun, 2004 1 commit
    • Tom Lane's avatar
      Adjust our timezone library to use pg_time_t (typedef'd as int64) in · 921d749b
      Tom Lane authored
      place of time_t, as per prior discussion.  The behavior does not change
      on machines without a 64-bit-int type, but on machines with one, which
      is most, we are rid of the bizarre boundary behavior at the edges of
      the 32-bit-time_t range (1901 and 2038).  The system will now treat
      times over the full supported timestamp range as being in your local
      time zone.  It may seem a little bizarre to consider that times in
      4000 BC are PST or EST, but this is surely at least as reasonable as
      propagating Gregorian calendar rules back that far.
      
      I did not modify the format of the zic timezone database files, which
      means that for the moment the system will not know about daylight-savings
      periods outside the range 1901-2038.  Given the way the files are set up,
      it's not a simple decision like 'widen to 64 bits'; we have to actually
      think about the range of years that need to be supported.  We should
      probably inquire what the plans of the upstream zic people are before
      making any decisions of our own.
      921d749b
  15. 22 May, 2004 1 commit
  16. 21 May, 2004 1 commit
  17. 05 Apr, 2004 1 commit
  18. 11 Feb, 2004 1 commit
    • Tom Lane's avatar
      Commit the reasonably uncontroversial parts of J.R. Nield's PITR patch, to · c3c09be3
      Tom Lane authored
      wit: Add a header record to each WAL segment file so that it can be reliably
      identified.  Avoid splitting WAL records across segment files (this is not
      strictly necessary, but makes it simpler to incorporate the header records).
      Make WAL entries for file creation, deletion, and truncation (as foreseen but
      never implemented by Vadim).  Also, add support for making XLOG_SEG_SIZE
      configurable at compile time, similarly to BLCKSZ.  Fix a couple bugs I
      introduced in WAL replay during recent smgr API changes.  initdb is forced
      due to changes in pg_control contents.
      c3c09be3
  19. 10 Feb, 2004 2 commits
    • Tom Lane's avatar
      Centralize implementation of delay code by creating a pg_usleep() · 58f337a3
      Tom Lane authored
      subroutine in src/port/pgsleep.c.  Remove platform dependencies from
      miscadmin.h and put them in port.h where they belong.  Extend recent
      vacuum cost-based-delay patch to apply to VACUUM FULL, ANALYZE, and
      non-btree index vacuuming.
      
      By the way, where is the documentation for the cost-based-delay patch?
      58f337a3
    • Tom Lane's avatar
      Restructure smgr API as per recent proposal. smgr no longer depends on · 87bd9563
      Tom Lane authored
      the relcache, and so the notion of 'blind write' is gone.  This should
      improve efficiency in bgwriter and background checkpoint processes.
      Internal restructuring in md.c to remove the not-very-useful array of
      MdfdVec objects --- might as well just use pointers.
      Also remove the long-dead 'persistent main memory' storage manager (mm.c),
      since it seems quite unlikely to ever get resurrected.
      87bd9563
  20. 26 Jan, 2004 1 commit
  21. 09 Jan, 2004 1 commit
  22. 07 Jan, 2004 1 commit
  23. 02 Dec, 2003 1 commit
  24. 29 Nov, 2003 1 commit
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  25. 16 Oct, 2003 1 commit
    • Tom Lane's avatar
      Fix bad interaction between NOTIFY processing and V3 extended query · 90b22029
      Tom Lane authored
      protocol, per report from Igor Shevchenko.  NOTIFY thought it could
      do its thing if transaction blockState is TBLOCK_DEFAULT, but in
      reality it had better check the low-level transaction state is
      TRANS_DEFAULT as well.  Formerly it was not possible to wait for the
      client in a state where the first is true and the second is not ...
      but now we can have such a state.  Minor cleanup in StartTransaction()
      as well.
      90b22029
  26. 28 Sep, 2003 1 commit
  27. 25 Sep, 2003 1 commit
  28. 24 Sep, 2003 1 commit
    • Tom Lane's avatar
      Repair some REINDEX problems per recent discussions. The relcache is · a56a016c
      Tom Lane authored
      now able to cope with assigning new relfilenode values to nailed-in-cache
      indexes, so they can be reindexed using the fully crash-safe method.  This
      leaves only shared system indexes as special cases.  Remove the 'index
      deactivation' code, since it provides no useful protection in the shared-
      index case.  Require reindexing of shared indexes to be done in standalone
      mode, but remove other restrictions on REINDEX.  -P (IgnoreSystemIndexes)
      now prevents using indexes for lookups, but does not disable index updates.
      It is therefore safe to allow from PGOPTIONS.  Upshot: reindexing system catalogs
      can be done without a standalone backend for all cases except
      shared catalogs.
      a56a016c
  29. 08 Aug, 2003 1 commit
  30. 04 Aug, 2003 2 commits
  31. 21 Jul, 2003 1 commit
  32. 14 May, 2003 1 commit
  33. 02 May, 2003 1 commit
    • Tom Lane's avatar
      Portal and memory management infrastructure for extended query protocol. · de28dc9a
      Tom Lane authored
      Both plannable queries and utility commands are now always executed
      within Portals, which have been revamped so that they can handle the
      load (they used to be good only for single SELECT queries).  Restructure
      code to push command-completion-tag selection logic out of postgres.c,
      so that it won't have to be duplicated between simple and extended queries.
      initdb forced due to addition of a field to Query nodes.
      de28dc9a