aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/misc/guc.c
Commit message (Collapse)AuthorAge
* Avoid crashing when restoring a saved GUC session_authorization valueTom Lane2004-08-11
| | | | that refers to a now-deleted userid. Per gripe from Chris Ochs.
* Do a direct probe during postmaster startup to determine the maximumTom Lane2004-02-23
| | | | | | number of openable files and the number already opened. This eliminates depending on sysconf(_SC_OPEN_MAX), and allows much saner behavior on platforms where open-file slots are used up by semaphores.
* zero_damaged_pages must absolutely NOT be marked GUC_DISALLOW_IN_FILE,Tom Lane2003-11-07
| | | | | else it cannot be used to handle failures detected during WAL replay. Fortunately this flag isn't actually enforced yet, but get it right.
* Cleanup on --help-config: Now called --describe-config, no further options,Peter Eisentraut2003-10-18
| | | | | machine readable, without headers, not sorted. Parameter descriptions adjusted to fit first sentence + rest convention.
* Have log_min_duration_statement = 0 always print duration/statement.Bruce Momjian2003-10-08
| | | | | | Change log line to be "duration: ms query:" Indent multi-line queries with a tab in the server logs.
* Add GUC parameter check_function_bodies to control whether validationTom Lane2003-10-03
| | | | | | | of function bodies is done at CREATE FUNCTION time. This is normally true but can be set false to avoid problems with forward references, wrong schema search path, etc. This is just the backend patch, still need to adjust pg_dump to make use of it.
* More message editing, some suggested by Alvaro HerreraPeter Eisentraut2003-09-29
|
* Various message fixes, among those fixes for the previous round of fixesPeter Eisentraut2003-09-26
|
* Message editing: remove gratuitous variations in message wording, standardizePeter Eisentraut2003-09-25
| | | | | terms, add some clarifications, fix some untranslatable attempts at dynamic message building.
* Improve a couple of error messages per suggestions from Alvaro Herrera.Tom Lane2003-09-15
|
* Consistenly lowercase GUC variable names, in docs and error messages.Bruce Momjian2003-09-11
|
* Remove geqo_random_seed parameter. Having geqo reset the global random()Tom Lane2003-09-07
| | | | | | | | 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.
* Allow non-super users to set log_duration to true, then false, when theBruce Momjian2003-09-04
| | | | | administrator has not turned it on, and fix other PGC_USERLIMIT variables.
* Pass session_authorization to the client and make psql update its promptPeter Eisentraut2003-09-03
| | | | accordingly.
* Do not pass server_encoding to the client.Peter Eisentraut2003-09-01
| | | | | | libpq, talking to an old server, should assume SQL_ASCII as the default client encoding, because that is what the server will actually use (not the server encoding).
* Rename DoIt to changeVar, for clarity.Bruce Momjian2003-09-01
|
* Mop-up for previous change to determine default shared_buffers andTom Lane2003-08-26
| | | | | | max_connections at initdb time. Get rid of DEF_NBUFFERS and DEF_MAXBACKENDS macros, which aren't doing anything useful anymore, and put more likely defaults into postgresql.conf.sample.
* Somebody forgot to include any actual documentation for ADD_MISSING_FROM.Tom Lane2003-08-17
|
* Rewriter and planner should use only resno, not resname, to identifyTom Lane2003-08-11
| | | | | | | target columns in INSERT and UPDATE targetlists. Don't rely on resname to be accurate in ruleutils, either. This fixes bug reported by Donald Fraser, in which renaming a column referenced in a rule did not work very well.
* Fix some copyright notices that weren't updated. Improve copyright toolTom Lane2003-08-04
| | | | so it won't miss 'em again.
* pgindent run.Bruce Momjian2003-08-04
|
* Fix my own mistake in GUC variable annotation.Tom Lane2003-08-01
|
* Adjust 'permission denied' messages to be more useful and consistent.Tom Lane2003-08-01
|
* Apply (a somewhat revised version of) Greg Mullane's patch to eliminateTom Lane2003-07-29
| | | | | | | | | 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.
* Code review for recent GUC changes --- try to make it less obvious thatTom Lane2003-07-28
| | | | | these things were added at different times by different people ;-). Includes Aizaz Ahmed's patch to remove duplicate array in help_config.c.
* There was enough code drift since this patch, that a couple of bugsBruce Momjian2003-07-28
| | | | | | | | | | | materialized. New items have been added to GucContext and GucSource enums, but of course they were not added to the corresponding GucContextName[] and GucSourceName[] arrays in the patch. Here's a new patch to fix the resulting bugs. Joe Conway
* A visit from the message-style police ...Tom Lane2003-07-28
|
* > Joe Conway <mail@joeconway.com> writes:Bruce Momjian2003-07-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | >>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
* Error message editing in backend/utils (except /adt).Tom Lane2003-07-25
|
* Add GUC parameter to control rendezvous name.Bruce Momjian2003-07-22
|
* Cause SHOW DATESTYLE to produce a string that will be accepted by SETTom Lane2003-07-15
| | | | | | DATESTYLE, for instance 'SQL, European' instead of 'SQL with European conventions'. Per gripe a month or two back from Barry Lind.
* Add special checks for non-super-user setting LOG_MIN_DURATION_STATEMENTBruce Momjian2003-07-09
| | | | to zero.
* Add new USERLIMIT GUC source level so certain options can be disabledBruce Momjian2003-07-09
| | | | | | | or increased only by super-users. This fixes problems caused by making certain variables SUSET for security reasons.
* Add --help-config facility to dump information about GUC parametersTom Lane2003-07-04
| | | | | | without needing a running backend. Reorder postgresql.conf.sample to match new layout of runtime.sgml. This commit re-adds work lost in Wednesday's crash.
* Add GUC option log_error_verbosity to control which fields of errorTom Lane2003-06-30
| | | | | | reports get put into the postmaster log. Options are TERSE, DEFAULT, VERBOSE, with the same behavior as implemented on the client side in libpq.
* Add is_superuser parameter reporting, soon to be used by psql.Tom Lane2003-06-27
|
* Add add_missing_from GUC variable.Bruce Momjian2003-06-11
| | | | Nigel J. Andrews
* Make "log_min_duration_statement" SUSET --- will be adjusted with newBruce Momjian2003-06-11
| | | | USERLIMIT patch.
* Add log_min_duration_statement.Bruce Momjian2003-06-11
| | | | Christopher Kings-Lynne
* Remove lock* GUC variables from postgresql.conf.Bruce Momjian2003-06-11
| | | | Document why certain GUC variables aren't in postgresql.conf.
* Fix things so that an error occuring during standalone-backend processingTom Lane2003-05-28
| | | | | in initdb will result in exit(1), allowing the initdb script to realize that there's something wrong.
* Make log_ GUC settings controllable only by super-users, so non-superBruce Momjian2003-05-27
| | | | users can't turn it off.
* Make debug_ GUC varables output DEBUG1 rather than LOG, and mention inBruce Momjian2003-05-27
| | | | | docs that CLIENT/LOG_MIN_MESSAGES now controls debug_* output location. Doc changes included.
* Backend support for autocommit removed, per recent discussions. TheTom Lane2003-05-14
| | | | | | only remnant of this failed experiment is that the server will take SET AUTOCOMMIT TO ON. Still TODO: provide some client-side autocommit logic in libpq.
* Restructure command destination handling so that we pass aroundTom Lane2003-05-06
| | | | | | | | | | | | | | 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.
* SECOND ATTEMPTBruce Momjian2003-05-02
| | | | Dump/read non-default GUC values for use by exec'ed backend, for Win32.
* Back out second part of patch.Bruce Momjian2003-05-02
|
* Back out last commit --- wrong patch.Bruce Momjian2003-05-02
|
* In the continuing saga of FE/BE protocol revisions, add reporting ofTom Lane2003-04-25
| | | | | | | | | | | | | 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.)
* Add code to apply some simple sanity checks to the header fields of aTom Lane2003-03-28
| | | | | | | | page when it's read in, per pghackers discussion around 17-Feb. Add a GUC variable zero_damaged_pages that causes the response to be a WARNING followed by zeroing the page, rather than the normal ERROR; this is per Hiroshi's suggestion that there needs to be a way to get at the data in the rest of the table.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 15:06:06 +0000