1. 29 7月, 2003 1 次提交
  2. 27 7月, 2003 1 次提交
    • B
      > Joe Conway <mail@joeconway.com> writes: · 38fb906f
      Bruce Momjian 提交于
      >>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
  3. 22 7月, 2003 1 次提交
  4. 10 7月, 2003 1 次提交
  5. 09 7月, 2003 1 次提交
  6. 12 6月, 2003 1 次提交
  7. 07 5月, 2003 1 次提交
    • T
      Restructure command destination handling so that we pass around · 79913910
      Tom Lane 提交于
      DestReceiver pointers instead of just CommandDest values.  The DestReceiver
      is made at the point where the destination is selected, rather than
      deep inside the executor.  This cleans up the original kluge implementation
      of tstoreReceiver.c, and makes it easy to support retrieving results
      from utility statements inside portals.  Thus, you can now do fun things
      like Bind and Execute a FETCH or EXPLAIN command, and it'll all work
      as expected (e.g., you can Describe the portal, or use Execute's count
      parameter to suspend the output partway through).  Implementation involves
      stuffing the utility command's output into a Tuplestore, which would be
      kind of annoying for huge output sets, but should be quite acceptable
      for typical uses of utility commands.
      79913910
  8. 03 5月, 2003 3 次提交
  9. 26 4月, 2003 1 次提交
    • T
      In the continuing saga of FE/BE protocol revisions, add reporting of · 9cbaf721
      Tom Lane 提交于
      initial values and runtime changes in selected parameters.  This gets
      rid of the need for an initial 'select pg_client_encoding()' query in
      libpq, bringing us back to one message transmitted in each direction
      for a standard connection startup.  To allow server version to be sent
      using the same GUC mechanism that handles other parameters, invent the
      concept of a never-settable GUC parameter: you can 'show server_version'
      but it's not settable by any GUC input source.  Create 'lc_collate' and
      'lc_ctype' never-settable parameters so that people can find out these
      settings without need for pg_controldata.  (These side ideas were all
      discussed some time ago in pgsql-hackers, but not yet implemented.)
      9cbaf721
  10. 15 11月, 2002 2 次提交
  11. 22 10月, 2002 1 次提交
  12. 05 9月, 2002 1 次提交
  13. 02 9月, 2002 2 次提交
  14. 31 7月, 2002 1 次提交
    • B
      Here are two patches. The guc_and_tablefunc patch addresses the two · 23a8b77d
      Bruce Momjian 提交于
      changes mentioned above, and also adds a new function to the tablefunc
      API. The tablefunc API change adds the following function:
      
      * Oid foidGetTypeId(Oid foid) - Get a function's typeid given the
      * function Oid. Use this together with TypeGetTupleDesc() to get a
      * TupleDesc which is derived from the function's declared return type.
      
      In the next post I'll send the contrib/tablefunc patch, which
      illustrates the usage of this new function. Also attached is a doc patch
      for this change. The doc patch also adds a function that I failed to
      document previously.
      
      Joe Conway
      23a8b77d
  15. 20 7月, 2002 2 次提交
  16. 17 5月, 2002 1 次提交
    • T
      Merge the last few variable.c configuration variables into the generic · f0811a74
      Tom Lane 提交于
      GUC support.  It's now possible to set datestyle, timezone, and
      client_encoding from postgresql.conf and per-database or per-user
      settings.  Also, implement rollback of SET commands that occur in a
      transaction that later fails.  Create a SET LOCAL var = value syntax
      that sets the variable only for the duration of the current transaction.
      All per previous discussions in pghackers.
      f0811a74
  17. 24 3月, 2002 1 次提交
  18. 02 3月, 2002 1 次提交
  19. 23 2月, 2002 1 次提交
  20. 06 11月, 2001 1 次提交
  21. 28 10月, 2001 1 次提交
  22. 25 10月, 2001 1 次提交
  23. 01 10月, 2001 1 次提交
  24. 19 6月, 2001 1 次提交
  25. 13 6月, 2001 1 次提交
    • T
      Extend GUC concepts of parse_hook and assign_hook to all four supported · 2938eec7
      Tom Lane 提交于
      datatypes, not only strings.  parse_hook is useless for bool, I suppose,
      but it seems possibly useful for int and double to apply variable-specific
      constraints that are more complex than simple range limits.  assign_hook
      is definitely useful for all datatypes --- we need it right now for bool
      to support date cache reset when changing Australian timezone rule setting.
      Also, clean up some residual problems with the reset all/show all patch,
      including memory leaks and mistaken reset of PostPortNumber.  It seems
      best that RESET ALL not touch variables that don't have SUSET or
      USERSET context.
      2938eec7
  26. 07 6月, 2001 1 次提交
  27. 22 3月, 2001 1 次提交
  28. 10 2月, 2001 1 次提交
    • T
      Restructure the key include files per recent pghackers discussion: there · d08741ea
      Tom Lane 提交于
      are now separate files "postgres.h" and "postgres_fe.h", which are meant
      to be the primary include files for backend .c files and frontend .c files
      respectively.  By default, only include files meant for frontend use are
      installed into the installation include directory.  There is a new make
      target 'make install-all-headers' that adds the whole content of the
      src/include tree to the installed fileset, for use by people who want to
      develop server-side code without keeping the complete source tree on hand.
      Cleaned up a whole lot of crufty and inconsistent header inclusions.
      d08741ea
  29. 28 7月, 2000 1 次提交
  30. 04 7月, 2000 1 次提交
  31. 23 6月, 2000 1 次提交
    • P
      Second pass over run-time configuration system. Adjust priorities on some · c4465095
      Peter Eisentraut 提交于
      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
  32. 31 5月, 2000 1 次提交
    • P
      The heralded `Grand Unified Configuration scheme' (GUC) · 6a68f426
      Peter Eisentraut 提交于
      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