Skip to content
Snippets Groups Projects
  1. Jul 05, 2000
  2. Jul 04, 2000
  3. Jul 03, 2000
  4. Jul 02, 2000
  5. Jul 01, 2000
  6. Jun 30, 2000
    • Peter Eisentraut's avatar
      Fixes for Solaris/cc suggested by <pgsql-hackers@thewrittenword.com> · 385470f8
      Peter Eisentraut authored
      Don't use DISABLE_COMPLEX_MACRO on Solaris. Don't define the
      replacement function in the header file. Use -KPIC, not -K PIC.
      Use CC to link C++ libraries, not ld/ar.
      
      Eliminate file not found warnings in tcl build code.
      385470f8
    • Tom Lane's avatar
      RemoveView was doing things the hard way... · 3513f4d1
      Tom Lane authored
      3513f4d1
    • Tom Lane's avatar
      Use a private memory context to store rule information in each relcache · b41f4ab8
      Tom Lane authored
      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
  7. Jun 29, 2000
  8. Jun 28, 2000
    • Tom Lane's avatar
      5ac1eac2
    • Tom Lane's avatar
      First phase of memory management rewrite (see backend/utils/mmgr/README · 1aebc361
      Tom Lane authored
      for details).  It doesn't really do that much yet, since there are no
      short-term memory contexts in the executor, but the infrastructure is
      in place and long-term contexts are handled reasonably.  A few long-
      standing bugs have been fixed, such as 'VACUUM; anything' in a single
      query string crashing.  Also, out-of-memory is now considered a
      recoverable ERROR, not FATAL.
      Eliminate a large amount of crufty, now-dead code in and around
      memory management.
      Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and
      backend startup.
      1aebc361
  9. Jun 27, 2000
  10. Jun 25, 2000
  11. Jun 23, 2000
    • Peter Eisentraut's avatar
      Second pass over run-time configuration system. Adjust priorities on some · c4465095
      Peter Eisentraut authored
      option settings. Sort out SIGHUP vs BACKEND -- there is no total ordering
      here, so make explicit checks. Add comments explaining all of this.
      Removed permissions check on SHOW command.
      
      Add examine_subclass to the game, rename to SQL_inheritance to fit the
      official data model better. Adjust documentation.
      
      Standalone backend needs to reset all options before it starts. To
      facilitate that, have IsUnderPostmaster be set by the postmaster itself,
      don't wait for the magic -p switch.
      
      Also make sure that all environment variables and argv's survive
      init_ps_display(). Use strdup where necessary.
      
      Have initdb make configuration files (postgresql.conf, pg_hba.conf) mode
      0600 -- having configuration files is no fun if you can't edit them.
      c4465095
Loading