1. 22 Jul, 2000 1 commit
  2. 21 Jul, 2000 1 commit
  3. 22 Jun, 2000 1 commit
    • 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
  4. 09 Jun, 2000 1 commit
  5. 27 Mar, 2000 1 commit
  6. 26 Mar, 2000 1 commit
  7. 15 Mar, 2000 1 commit
    • Tom Lane's avatar
      Tweak GROUP BY so that it will still accept result-column names, but only · 1763a7c1
      Tom Lane authored
      after trying to resolve the item as an input-column name.  This allows us
      to be compliant with the SQL92 spec for queries that fall within the spec,
      while still accepting the same out-of-spec queries as 6.5 did.  You'll only
      lose if there is an output column name that is the same as an input
      column name, but doesn't refer to the same value.  7.0 will interpret
      such a GROUP BY spec differently than 6.5 did.  No way around that, because
      6.5 was clearly not spec compliant.
      1763a7c1
  8. 21 Feb, 2000 1 commit
  9. 27 Jan, 2000 1 commit
    • Tom Lane's avatar
      Redesign DISTINCT ON as discussed in pgsql-sql 1/25/00: syntax is now · dd979f66
      Tom Lane authored
      SELECT DISTINCT ON (expr [, expr ...]) targetlist ...
      and there is a check to make sure that the user didn't specify an ORDER BY
      that's incompatible with the DISTINCT operation.
      Reimplement nodeUnique and nodeGroup to use the proper datatype-specific
      equality function for each column being compared --- they used to do
      bitwise comparisons or convert the data to text strings and strcmp().
      (To add insult to injury, they'd look up the conversion functions once
      for each tuple...)  Parse/plan representation of DISTINCT is now a list
      of SortClause nodes.
      initdb forced by querytree change...
      dd979f66
  10. 13 Dec, 1999 1 commit
  11. 06 Aug, 1999 1 commit
  12. 22 Jul, 1999 1 commit
  13. 16 Jul, 1999 1 commit
  14. 15 Jul, 1999 1 commit
  15. 14 Jul, 1999 1 commit
  16. 14 Jun, 1999 1 commit
  17. 03 Jun, 1999 1 commit
  18. 12 May, 1999 1 commit
  19. 10 May, 1999 1 commit
  20. 06 Apr, 1999 1 commit
  21. 19 Mar, 1999 1 commit
  22. 13 Feb, 1999 1 commit
  23. 02 Feb, 1999 1 commit
  24. 29 Dec, 1998 1 commit
  25. 18 Dec, 1998 1 commit
  26. 30 Oct, 1998 1 commit
  27. 15 Oct, 1998 1 commit
  28. 30 Sep, 1998 1 commit
  29. 25 Sep, 1998 1 commit
  30. 07 Sep, 1998 1 commit
  31. 01 Sep, 1998 1 commit
  32. 13 May, 1998 1 commit