1. 16 Nov, 2003 1 commit
  2. 13 Nov, 2003 3 commits
  3. 07 Nov, 2003 1 commit
  4. 06 Nov, 2003 1 commit
  5. 18 Oct, 2003 1 commit
  6. 08 Oct, 2003 1 commit
  7. 03 Oct, 2003 1 commit
  8. 29 Sep, 2003 1 commit
  9. 26 Sep, 2003 1 commit
  10. 25 Sep, 2003 1 commit
  11. 15 Sep, 2003 1 commit
  12. 11 Sep, 2003 1 commit
  13. 07 Sep, 2003 1 commit
    • Tom Lane's avatar
      Remove geqo_random_seed parameter. Having geqo reset the global random() · 48beecda
      Tom Lane authored
      sequence every time it's called is bogus --- it interferes with user
      control over the seed, and actually decreases randomness overall
      (because a seed based on time(NULL) is pretty predictable).  If you really
      want a reproducible result from geqo, do 'set seed = 0' before planning
      a query.
      48beecda
  14. 04 Sep, 2003 1 commit
  15. 03 Sep, 2003 1 commit
  16. 01 Sep, 2003 2 commits
  17. 26 Aug, 2003 1 commit
  18. 17 Aug, 2003 1 commit
  19. 11 Aug, 2003 1 commit
  20. 04 Aug, 2003 2 commits
  21. 01 Aug, 2003 2 commits
  22. 29 Jul, 2003 1 commit
    • Tom Lane's avatar
      Apply (a somewhat revised version of) Greg Mullane's patch to eliminate · 9c2a7c22
      Tom Lane authored
      heuristic determination of day vs month in date/time input.  Add the
      ability to specify that input is interpreted as yy-mm-dd order (which
      formerly worked, but only for yy greater than 31).  DateStyle's input
      component now has the preferred spellings DMY, MDY, or YMD; the older
      keywords European and US are now aliases for the first two of these.
      Per recent discussions on pgsql-general.
      9c2a7c22
  23. 28 Jul, 2003 3 commits
  24. 27 Jul, 2003 1 commit
    • Bruce Momjian's avatar
      > Joe Conway <mail@joeconway.com> writes: · 38fb906f
      Bruce Momjian authored
      >>ISTM that "source" is worth knowing.
      >
      > Hm, possibly.  Any other opinions?
      
      This version has the seven fields I proposed, including "source". Here's
      an example that shows why I think it's valuable:
      
      regression=# \x
      Expanded display is on.
      regression=# select * from pg_settings where name = 'enable_seqscan';
      -[ RECORD 1 ]-----------
      name    | enable_seqscan
      setting | on
      context | user
      vartype | bool
      source  | default
      min_val |
      max_val |
      
      regression=# update pg_settings set setting = 'off' where name =
      'enable_seqscan';
      -[ RECORD 1 ]---
      set_config | off
      
      regression=# select * from pg_settings where name = 'enable_seqscan';
      -[ RECORD 1 ]-----------
      name    | enable_seqscan
      setting | off
      context | user
      vartype | bool
      source  | session
      min_val |
      max_val |
      
      regression=# alter user postgres set enable_seqscan to 'off';
      ALTER USER
      
      (log out and then back in again)
      
      regression=# \x
      Expanded display is on.
      regression=# select * from pg_settings where name = 'enable_seqscan';
      -[ RECORD 1 ]-----------
      name    | enable_seqscan
      setting | off
      context | user
      vartype | bool
      source  | user
      min_val |
      max_val |
      
      In the first case, enable_seqscan is set to its default value. After
      setting it to off, it is obvious that the value has been changed for the
      session only. In the third case, you can see that the value has been set
      specifically for the user.
      
      Joe Conway
      38fb906f
  25. 25 Jul, 2003 1 commit
  26. 22 Jul, 2003 1 commit
  27. 15 Jul, 2003 1 commit
  28. 09 Jul, 2003 2 commits
  29. 04 Jul, 2003 1 commit
  30. 30 Jun, 2003 1 commit
  31. 27 Jun, 2003 1 commit
  32. 11 Jun, 2003 1 commit