- 07 4月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
> >>with allowed values of "all, mod, ddl, none" with default "none". OK, here is a patch that implements #1. Here is sample output: test=> set client_min_messages = 'log'; SET test=> set log_statement = 'mod'; SET test=> select 1; ?column? ---------- 1 (1 row) test=> update test set x=1; LOG: statement: update test set x=1; ERROR: relation "test" does not exist test=> update test set x=1; LOG: statement: update test set x=1; ERROR: relation "test" does not exist test=> copy test from '/tmp/x'; LOG: statement: copy test from '/tmp/x'; ERROR: relation "test" does not exist test=> copy test to '/tmp/x'; ERROR: relation "test" does not exist test=> prepare xx as select 1; PREPARE test=> prepare xx as update x set y=1; LOG: statement: prepare xx as update x set y=1; ERROR: relation "x" does not exist test=> explain analyze select 1;; QUERY PLAN ------------------------------------------------------------------------------------ Result (cost=0.00..0.01 rows=1 width=0) (actual time=0.006..0.007 rows=1 loops=1) Total runtime: 0.046 ms (2 rows) test=> explain analyze update test set x=1; LOG: statement: explain analyze update test set x=1; ERROR: relation "test" does not exist test=> explain update test set x=1; ERROR: relation "test" does not exist It checks PREPARE and EXECUTE ANALYZE too. The log_statement values are 'none', 'mod', 'ddl', and 'all'. For 'all', it prints before the query is parsed, and for ddl/mod, it does it right after parsing using the node tag (or command tag for CREATE/ALTER/DROP), so any non-parse errors will print after the log line.
-
- 05 4月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
variable to control logoutput location on Unix and Win32. Magnus Hagander
-
- 25 3月, 2004 1 次提交
-
-
由 Tom Lane 提交于
is measured in kilobytes and checked against actual physical execution stack depth, as per my proposal of 30-Dec. This gives us a fairly bulletproof defense against crashing due to runaway recursive functions.
-
- 24 3月, 2004 1 次提交
-
-
由 Neil Conway 提交于
parameter description: postgresql.conf is not the place for documentating the functionality of a GUC var.
-
- 23 3月, 2004 1 次提交
-
-
由 Tom Lane 提交于
listen_addresses parameter, as per recent discussion. The default behavior is now to listen on localhost, which eliminates the need for the -i postmaster switch in many scenarios. Andrew Dunstan
-
- 15 3月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
Functionality superceeded by log_line_prefix. Andrew Dunstan
-
- 09 3月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
#log_line_prefix = '' # e.g. '<%u%%%d> ' # %u=user name %d=database name # %r=remote host and port # %p=PID %t=timestamp %i=command tag # %c=session id %l=session line number # %s=session start timestamp # %x=stop here in non-session processes # %%='%' Andrew Dunstan
-
- 17 2月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
bitrotted) to allow the logging of the end of a session, enabled by the config setting "log_disconnections". Andrew Dunstan
-
由 Bruce Momjian 提交于
-
- 07 2月, 2004 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 04 2月, 2004 2 次提交
-
-
由 Jan Wieck 提交于
Jan
-
由 Tom Lane 提交于
Make btree index creation and initial validation of foreign-key constraints use maintenance_work_mem rather than work_mem as their memory limit. Add some code to guc.c to allow these variables to be referenced by their old names in SHOW and SET commands, for backwards compatibility.
-
- 25 1月, 2004 1 次提交
-
-
由 Jan Wieck 提交于
done by the background writer between writing dirty blocks and napping. none (default) no action sync bgwriter calls smgrsync() causing a sync(2) A global sync() is only good on dedicated database servers, so more flush methods should be added in the future. Jan
-
- 24 1月, 2004 1 次提交
-
-
由 Tom Lane 提交于
that it's good to join where there are join clauses rather than where there are not. Also enable it to generate bushy plans at need, so that it doesn't fail in the presence of multiple IN clauses containing sub-joins. These changes appear to improve the behavior enough that we can substantially reduce the default pool size and generations count, thereby decreasing the runtime, and yet get as good or better plans as we were getting in 7.4. Consequently, adjust the default GEQO parameters. I also modified the way geqo_effort is used so that it affects both population size and number of generations; it's now useful as a single control to adjust the GEQO runtime-vs-plan-quality tradeoff. Bump geqo_threshold to 12, since even with these changes GEQO seems to be slower than the regular planner at 11 relations.
-
- 22 1月, 2004 1 次提交
-
-
由 Tom Lane 提交于
default value for geqo_effort is supposed to be 40, not 1. The actual 'genetic' component of the GEQO algorithm has been practically disabled since 7.1 because of this mistake. Improve documentation while at it.
-
- 02 12月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
proposal for eventually deprecating OIDs on user tables that I posted earlier to pgsql-hackers. pg_dump now always specifies WITH OIDS or WITHOUT OIDS when dumping a table. The documentation has been updated. Neil Conway
-
- 19 11月, 2003 1 次提交
-
-
由 Jan Wieck 提交于
This first part of the background writer does no syncing at all. It's only purpose is to keep the LRU heads clean so that regular backends seldom to never have to call write(). Jan
-
- 17 11月, 2003 1 次提交
-
-
由 Jan Wieck 提交于
debug_shared_buffers = <seconds> as per previous discussion. Jan
-
- 13 11月, 2003 3 次提交
- 08 10月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Change log line to be "duration: ms query:" Indent multi-line queries with a tab in the server logs.
-
- 04 10月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 07 9月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 26 8月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 17 8月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
"syslog" option.) By the way: The "virtual_host" parameter is a bad name for that particular option, I think. "Virtual host" signals that PostgreSQL will behave differently according to which IP address it's contacted (like Apache's virtual host support which makes the web-server serve different sites according to different criteria). A better word for the options would be "tcpip_listen_addr" or something like that. Troels Arvin
-
- 29 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 23 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 19 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 15 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
and 100 respectively, if the platform will allow it. initdb selects values that are not too large to allow the postmaster to start, and places these values in the installed postgresql.conf file. This allows us to continue to start up out-of-the-box on platforms with small SHMMAX, while having somewhat-realistic default settings on platforms with reasonable SHMMAX. Per recent pghackers discussion.
-
- 05 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 01 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
reports get put into the postmaster log. Options are TERSE, DEFAULT, VERBOSE, with the same behavior as implemented on the client side in libpq.
-
- 12 6月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
Nigel J. Andrews
-
由 Bruce Momjian 提交于
Christopher Kings-Lynne
-
- 11 6月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Document why certain GUC variables aren't in postgresql.conf.
-
- 14 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 19 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 04 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
find out about it is to read the documentation that tells you how dangerous it is. Add default_transaction_read_only to documentation; seems to have been overlooked in patch that added read-only transactions. Clean up check_guc comparison script, which has been suffering bit rot.
-
- 31 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 29 3月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-