Skip to content
Snippets Groups Projects
  1. Jul 04, 2000
    • Tom Lane's avatar
      Make toast-table creation and deletion work somewhat reliably. · cdeca5f5
      Tom Lane authored
      Don't go through pg_exec_query_dest(), but directly to the execution
      routines.  Also, extend parameter lists so that there's no need to
      change the global setting of allowSystemTableMods, a hack that was
      certain to cause trouble in the event of any error.
      cdeca5f5
    • Jan Wieck's avatar
      TOAST · 57d8080a
      Jan Wieck authored
          WARNING: This is actually broken - we have self-deadlocks
      	         due to concurrent changes in buffer management.
      			 Vadim and me are working on it.
      
      Jan
      57d8080a
  2. Jul 03, 2000
  3. Jun 28, 2000
    • 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
  4. 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
  5. Jun 19, 2000
    • Tom Lane's avatar
      Reimplement nodeMaterial to use a temporary BufFile (or even memory, if the · 1ee26b77
      Tom Lane authored
      materialized tupleset is small enough) instead of a temporary relation.
      This was something I was thinking of doing anyway for performance, and Jan
      says he needs it for TOAST because he doesn't want to cope with toasting
      noname relations.  With this change, the 'noname table' support in heap.c
      is dead code, and I have accordingly removed it.  Also clean up 'noname'
      plan handling in planner --- nonames are either sort or materialize plans,
      and it seems less confusing to handle them separately under those names.
      1ee26b77
  6. Jun 18, 2000
    • Tom Lane's avatar
      Get rid of IndexIsUniqueNoCache() kluge by the simple expedient of · edf0b5f0
      Tom Lane authored
      passing the index-is-unique flag to index build routines (duh! ...
      why wasn't it done this way to begin with?).  Aside from eliminating
      an eyesore, this should save a few milliseconds in btree index creation
      because a full scan of pg_index is not needed any more.
      edf0b5f0
  7. Jun 07, 2000
    • Peter Eisentraut's avatar
      Gen_fmgrtab.sh is strange: it is a platform dependent way (because it uses · e3059fc0
      Peter Eisentraut authored
      CPP) to create platform independent files. Unfortunately, that means that
      every config.status (or configure) run invariably causes a relink of the
      postmaster and also that we can't put these files in the distribution
      (usefully). So we make it a little smarter: when the output files already
      exist and it notices that it would recreate them in identical form, it
      doesn't touch them. In order to avoid re-running the make rule all the time
      we update a timestamp file instead.
      
      Update release_prep accordingly. Also make Gen_fmgrtab.sh use the awk that
      is detected at configure time, not necessarily named `awk' and have it check
      for exit statuses a little better.
      
      In other news... Remove USE_LOCALE from the templates, it was set to `no'
      everywhere anyway. Also remove YACC and YFLAGS from the templates, configure
      is smart enough to find bison or yacc itself. Use AC_PROG_YACC for that
      instead of the hand-crafted code. Do not set YFLAGS to `-d'. The make rules
      that need this flag should explicitly invoke it. YFLAGS should be a user
      variable. Update the makefiles to that effect.
      e3059fc0
  8. Jun 05, 2000
  9. May 31, 2000
    • Peter Eisentraut's avatar
      The heralded `Grand Unified Configuration scheme' (GUC) · 6a68f426
      Peter Eisentraut authored
      That means you can now set your options in either or all of $PGDATA/configuration,
      some postmaster option (--enable-fsync=off), or set a SET command. The list of
      options is in backend/utils/misc/guc.c, documentation will be written post haste.
      
      pg_options is gone, so is that pq_geqo config file. Also removed were backend -K,
      -Q, and -T options (no longer applicable, although -d0 does the same as -Q).
      
      Added to configure an --enable-syslog option.
      
      changed all callers from TPRINTF to elog(DEBUG)
      6a68f426
  10. May 30, 2000
  11. May 29, 2000
  12. May 28, 2000
    • Tom Lane's avatar
      First round of changes for new fmgr interface. fmgr itself and the · 0a7fb4e9
      Tom Lane authored
      key call sites are changed, but most called functions are still oldstyle.
      An exception is that the PL managers are updated (so, for example, NULL
      handling now behaves as expected in plperl and plpgsql functions).
      NOTE initdb is forced due to added column in pg_proc.
      0a7fb4e9
  13. Apr 12, 2000
  14. Feb 18, 2000
  15. Jan 26, 2000
    • Bruce Momjian's avatar
      Add: · 5c25d602
      Bruce Momjian authored
        * Portions Copyright (c) 1996-2000, PostgreSQL, Inc
      
      to all files copyright Regents of Berkeley.  Man, that's a lot of files.
      5c25d602
  16. Jan 19, 2000
  17. Jan 17, 2000
  18. Jan 16, 2000
  19. Jan 15, 2000
  20. Jan 11, 2000
  21. Jan 10, 2000
  22. Dec 20, 1999
  23. Dec 16, 1999
  24. Dec 13, 1999
  25. Dec 09, 1999
  26. Nov 24, 1999
  27. Nov 08, 1999
  28. Nov 04, 1999
    • Hiroshi Inoue's avatar
      Make it possible to execute crashed CREATE/DROP commands again. · 2e2189a5
      Hiroshi Inoue authored
      Now indexes of pg_class and pg_type are unique indexes
      and guarantee the uniqueness of correponding attributes.
      heap_create() was changed to take another boolean parameter
      which allows to postpone the creation of disk file.
      The name of rd_nonameunlinked was changed to rd_unlinked.
      It is used generally(not only for noname relations) now.
      Requires initdb.
      2e2189a5
  29. Oct 25, 1999
    • Tom Lane's avatar
      Standardize on MAXPGPATH as the size of a file pathname buffer, · 51f62d50
      Tom Lane authored
      eliminating some wildly inconsistent coding in various parts of the
      system.  I set MAXPGPATH = 1024 in config.h.in.  If anyone is really
      convinced that there ought to be a configure-time test to set the
      value, go right ahead ... but I think it's a waste of time.
      51f62d50
  30. Oct 06, 1999
  31. Sep 27, 1999
  32. Sep 18, 1999
    • Tom Lane's avatar
      Mega-commit to make heap_open/heap_openr/heap_close take an · bd272cac
      Tom Lane authored
      additional argument specifying the kind of lock to acquire/release (or
      'NoLock' to do no lock processing).  Ensure that all relations are locked
      with some appropriate lock level before being examined --- this ensures
      that relevant shared-inval messages have been processed and should prevent
      problems caused by concurrent VACUUM.  Fix several bugs having to do with
      mismatched increment/decrement of relation ref count and mismatched
      heap_open/close (which amounts to the same thing).  A bogus ref count on
      a relation doesn't matter much *unless* a SI Inval message happens to
      arrive at the wrong time, which is probably why we got away with this
      sloppiness for so long.  Repair missing grab of AccessExclusiveLock in
      DROP TABLE, ALTER/RENAME TABLE, etc, as noted by Hiroshi.
      Recommend 'make clean all' after pulling this update; I modified the
      Relation struct layout slightly.
      Will post further discussion to pghackers list shortly.
      bd272cac
  33. Sep 12, 1999
  34. Jul 19, 1999
  35. Jul 17, 1999
  36. Jul 16, 1999
Loading