1. 04 7月, 2000 16 次提交
  2. 03 7月, 2000 5 次提交
  3. 02 7月, 2000 7 次提交
  4. 01 7月, 2000 6 次提交
  5. 30 6月, 2000 3 次提交
    • T
      RemoveView was doing things the hard way... · 3513f4d1
      Tom Lane 提交于
      3513f4d1
    • T
      Use a private memory context to store rule information in each relcache · b41f4ab8
      Tom Lane 提交于
      entry that has rules.  This allows us to release the rule parsetrees
      on relcache flush without needing a working freeObject() routine.
      Formerly, the rule trees were leaked permanently at relcache flush.
      Also, clean up handling of rule creation and deletion --- there was
      not sufficient locking of the relation being modified, and there was
      no reliable notification of other backends that a relcache reload
      was needed.  Also, clean up relcache.c code so that scans of system
      tables needed to load a relcache entry are done in the caller's
      memory context, not in CacheMemoryContext.  This prevents any
      un-pfreed memory from those scans from becoming a permanent memory
      leak.
      b41f4ab8
    • B
      Fix quotes in /* */ comments in psql. · c9ec78a6
      Bruce Momjian 提交于
      c9ec78a6
  6. 29 6月, 2000 3 次提交
    • T
      Add test code to copy all parse/plan trees. Repair essential omissions · 43ba1b44
      Tom Lane 提交于
      in copyfuncs and equalfuncs exposed by regression tests.  We still have
      some work to do: these modules really ought to handle most or all of
      the utility statement node types.  But it's better than it was.
      43ba1b44
    • T
      Rearrange config.h entries into a more sensible order, and add some · 6a7b40d9
      Tom Lane 提交于
      documentation.  Let's try to keep this file a bit neater in future,
      hmm?  Also (to get back to the original point) update info about
      FUNC_MAX_ARGS, and add additional config symbols for debugging
      new memory management changes.
      6a7b40d9
    • T
      Remove freefuncs.c, which hasn't been used in a long time and is not · d1080d19
      Tom Lane 提交于
      worth the effort to continue to maintain.  Since freeObject() is not
      capable of coping with cases like multiple links to a node, it's
      unlikely that it ever will be useful again.  We now have memory
      context management that offers a faster and more reliable way of
      getting rid of arbitrary node trees (at the cost of having to know
      in advance of building the tree that you'll want to get rid of it).
      d1080d19