Skip to content
Snippets Groups Projects
  1. Sep 12, 2001
  2. Sep 11, 2001
  3. Sep 08, 2001
    • Peter Eisentraut's avatar
      Make the world somewhat safe for (not from) DELETE FROM pg_shadow; · c0d4d547
      Peter Eisentraut authored
      Assign the fixed user id 1 to the user created by initdb.
      A stand-alone backend will always set the user id to 1.
      (Consequently, the name of that user is no longer important.)
      
      In stand-alone mode, the user id 1 will have implicit superuser
      status, to allow repairs even if there are no users defined.
      
      Print a warning message when starting in stand-alone mode when no
      users are defined.
      
      Disallow dropping the current user and session user.
      
      Granting/revoking superuser status also grants/revokes usecatupd.
      (Previously, it would never grant it back.  This could lead to "deadlocks".)
      
      CREATE USER and CREATE GROUP will start allocating user ids at 100
      (unless explicitly specified), to prevent accidental creation of a
      superuser (plus some room for future extensions).
      c0d4d547
  4. Sep 07, 2001
    • Bruce Momjian's avatar
      Here is my much-promised patch to let people add UNIQUE constraints after · bd9b3280
      Bruce Momjian authored
      table creation time.  Big deal you say - but this patch is the basis of the
      next thing which is adding PRIMARY KEYs after table creation time.  (Which
      is currently impossible without twiddling catalogs)
      
      Rundown
      -------
      
      * I have made the makeObjectName function of analyze.c non-static, and
      exported it in analyze.h
      
      * I have included analyze.h and defrem.h into command.c, to support
      makingObjectNames and creating indices
      
      * I removed the 'case CONSTR_PRIMARY' clause so that it properly fails and
      says you can't add primary keys, rather than just doing nothing and
      reporting nothing!!!
      
      * I have modified the docs.
      
      Algorithm
      ---------
      
      * If name specified is null, search for a new valid constraint name.  I'm
      not sure if I should "lock" my generated name somehow tho - should I open
      the relation before doing this step?
      
      * Open relation in access exclusive mode
      
      * Check that the constraint does not already exist
      
      * Define the new index
      
      * Warn if they're doubling up on an existing index
      
      Christopher Kings-Lynne
      bd9b3280
    • Tom Lane's avatar
      Revert treatment of NOTIFY in rules to its pre-7.1 behavior: notify will · 17c03b30
      Tom Lane authored
      occur unconditionally, even if the rule should otherwise execute
      conditionally.  This is more useful than giving an error, even though it's
      not truly the correct behavior.  Per today's pghackers discussion.
      17c03b30
  5. Sep 06, 2001
  6. Sep 04, 2001
  7. Sep 03, 2001
  8. Aug 29, 2001
  9. Aug 28, 2001
    • Peter Eisentraut's avatar
      Include directory rearrangement · f5944af8
      Peter Eisentraut authored
      Client headers are no longer in a subdirectory, since they have been made
      namespace-clean.
      
      Internal libpq headers are in a private subdirectory.
      
      Server headers are in a private subdirectory.  pg_config has a new option
      to point there.
      f5944af8
  10. Aug 26, 2001
  11. Aug 25, 2001
  12. Aug 22, 2001
  13. Aug 21, 2001
    • Tom Lane's avatar
      Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in · f933766b
      Tom Lane authored
      pgsql-hackers.  pg_opclass now has a row for each opclass supported by each
      index AM, not a row for each opclass name.  This allows pg_opclass to show
      directly whether an AM supports an opclass, and furthermore makes it possible
      to store additional information about an opclass that might be AM-dependent.
      pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we
      previously expected the user to remember to provide in CREATE INDEX commands.
      Lossiness is no longer an index-level property, but is associated with the
      use of a particular operator in a particular index opclass.
      
      Along the way, IndexSupportInitialize now uses the syscaches to retrieve
      pg_amop and pg_amproc entries.  I find this reduces backend launch time by
      about ten percent, at the cost of a couple more special cases in catcache.c's
      IndexScanOK.
      
      Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane.
      
      initdb forced.
      f933766b
  14. Aug 16, 2001
    • Tom Lane's avatar
      Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type · d4f4b971
      Tom Lane authored
      has an alias SERIAL4 and a sister SERIAL8.  SERIAL8 is just the same
      except the created column is type int8 not int4.
      initdb forced.  Note this also breaks any chance of pg_upgrade from 7.1,
      unless we hack up pg_upgrade to drop and recreate sequences.  (Which is
      not out of the question, but I don't wanna do it.)
      d4f4b971
  15. Aug 15, 2001
  16. Aug 13, 2001
  17. Aug 12, 2001
  18. Aug 11, 2001
  19. Aug 10, 2001
  20. Aug 06, 2001
  21. Aug 05, 2001
  22. Aug 04, 2001
  23. Aug 03, 2001
  24. Jul 16, 2001
  25. Jul 15, 2001
  26. Jul 12, 2001
  27. Jul 11, 2001
  28. Jul 10, 2001
  29. Jul 01, 2001
Loading