- 06 7月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 03 7月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
documentation, to match SHOW.
-
- 01 7月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 26 6月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
literally. Add GUC variables: "escape_string_warning" - warn about backslashes in non-E strings "escape_string_syntax" - supports E'' syntax? "standard_compliant_strings" - treats backslashes literally in '' Update code to use E'' when escapes are used.
-
- 18 6月, 2005 1 次提交
-
-
由 Tom Lane 提交于
hacking by Alvaro Herrera and Tom Lane.
-
- 10 6月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
#log_line_prefix = '' # %u = user name # %d = database name # %r = remote host and port # %h = remote host # %p = PID # %t = timestamp # %m = timestamp with milliseconds # %i = command tag # %c = session id # %l = session line number # %s = session start timestamp # %x = transaction id # %q = stop here in non-session processes # %% = '%' # e.g. '<%u%%%d> '
-
由 Bruce Momjian 提交于
millisecond timestamps (%m) and remote host (%h). The milliseconds are useful for QPS measurements. Ed L.
-
- 05 6月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
Allow kerberos name and username case sensitivity to be specified from postgresql.conf. --------------------------------------------------------------------------- Here's an updated version of the patch, with the following changes: 1) No longer uses "service name" as "application version". It's instead hardcoded as "postgres". It could be argued that this part should be backpatched to 8.0, but it doesn't make a big difference until you can start changing it with GUC / connection parameters. This change only affects kerberos 5, not 4. 2) Now downcases kerberos usernames when the client is running on win32. 3) Adds guc option for "krb_caseins_users" to make the server ignore case mismatch which is required by some KDCs such as Active Directory. Off by default, per discussion with Tom. This change only affects kerberos 5, not 4. 4) Updated so it doesn't conflict with the rendevouz/bonjour patch already in ;-) Magnus Hagander
-
由 Bruce Momjian 提交于
-
- 15 5月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 4月, 2005 1 次提交
-
-
由 Tom Lane 提交于
logic operations during planning. Seems cleaner to create two new Path node types, instead --- this avoids duplication of cost-estimation code. Also, create an enable_bitmapscan GUC parameter to control use of bitmap plans.
-
- 08 4月, 2005 1 次提交
-
-
由 Neil Conway 提交于
the long-term plan for this behavior for quite some time, but it is only possible now that DELETE has a USING clause so that the user can join other tables in a DELETE statement without relying on this behavior.
-
- 24 3月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
currently does. This is now the default Win32 wal sync method because we perfer o_datasync to fsync. Also, change Win32 fsync to a new wal sync method called fsync_writethrough because that is the behavior of _commit, which is what is used for fsync on Win32. Backpatch to 8.0.X.
-
- 20 3月, 2005 1 次提交
-
-
由 Tom Lane 提交于
of the local buffer arena for temporary table access.
-
- 13 3月, 2005 1 次提交
-
-
由 Neil Conway 提交于
no longer include OIDs, unless WITH OIDS is specified or the default_with_oids configuration parameter is enabled. Update the docs accordingly.
-
- 05 3月, 2005 1 次提交
-
-
由 Tom Lane 提交于
the freelist, plus per-buffer spinlocks that protect access to individual shared buffer headers. This requires abandoning a global freelist (since the freelist is a global contention point), which shoots down ARC and 2Q as well as plain LRU management. Adopt a clock sweep algorithm instead. Preliminary results show substantial improvement in multi-backend situations.
-
- 06 11月, 2004 1 次提交
-
-
由 Tom Lane 提交于
clause implicitly whenever one is not given explicitly. Remove concept of a schema having an associated tablespace, and simplify the rules for selecting a default tablespace for a table or index. It's now just (a) explicit TABLESPACE clause; (b) default_tablespace if that's not an empty string; (c) database's default. This will allow pg_dump to use SET commands instead of tablespace clauses to determine object locations (but I didn't actually make it do so). All per recent discussions.
-
- 18 10月, 2004 1 次提交
-
-
由 Tom Lane 提交于
This does not disable the bgwriter process: it still has to wake up often enough to collect fsync requests from backends in a timely fashion. But it responds to the recent gripe about not being able to prevent the disk from being spun up constantly.
-
- 10 10月, 2004 1 次提交
-
-
由 Tom Lane 提交于
The vars are renamed to data_directory, config_file, hba_file, and ident_file, and are guaranteed to be set to accurate absolute paths during postmaster startup. This commit does not yet do anything about hiding path values from non-superusers.
-
- 08 10月, 2004 1 次提交
-
-
由 Tom Lane 提交于
Refactor code into something reasonably understandable, cause use of the feature to not fail in standalone backends or in EXEC_BACKEND case, fix sloppy guc.c table entries, make the documentation minimally usable.
-
- 29 9月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 22 9月, 2004 1 次提交
-
-
由 Neil Conway 提交于
log_line_prefix escapes. The escape sequence used for this is %x. %x previously meant "postmaster et al. stop here" -- this has been renamed to %q.
-
- 21 9月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 31 8月, 2004 1 次提交
-
-
由 Tom Lane 提交于
to allow DBA to choose the form in which log filenames reflect the current time. Also allow for truncating instead of appending to pre-existing files --- this is convenient when the log filename pattern rewrites the same names cyclically. Per Ed L.
-
- 13 8月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
and doesn't process forward slashes in the same way as external commands. Quoting the first argument to COPY does not convert forward to backward slashes, but COPY does properly process quoted forward slashes in the second argument. Win32 COPY works with quoted forward slashes in the first argument only if the current directory is the same as the directory of the first argument.
-
- 09 8月, 2004 1 次提交
-
-
由 Tom Lane 提交于
on other recent changes in runtime parameter list.
-
- 08 8月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 07 8月, 2004 2 次提交
-
-
由 Jan Wieck 提交于
Jan
-
由 Bruce Momjian 提交于
-
- 06 8月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
recommend that people go get Apache's rotatelogs program. Additional benefits are that configuration is done through GUC, rather than externally, and that the postmaster can monitor the log rotator and restart it after failure (though we certainly hope that won't happen often). Andreas Pflug, some rework by Tom Lane.
-
- 22 7月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
(fairly closely, I hope) to the current PL/Perl implementation. David Fetter
-
- 19 7月, 2004 1 次提交
-
-
由 Tom Lane 提交于
loose ends and a glaring lack of documentation, but it basically works. Simon Riggs with some editorialization by Tom Lane.
-
- 12 7月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 11 7月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
Add new postgresql.conf variables to point to data, pg_hba.conf, and pg_ident.conf files. Needs more documentation.
-
- 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.
-