- 11 4月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
calling proc_exit() directly. This should make SIGTERM more reliable.
-
- 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.
-
- 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.
-
- 22 3月, 2004 1 次提交
-
-
由 Tom Lane 提交于
errors in internally-generated queries, such as those submitted by plpgsql functions. Per recent discussions with Fabien Coelho.
-
- 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
-
- 21 2月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 17 2月, 2004 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
bitrotted) to allow the logging of the end of a session, enabled by the config setting "log_disconnections". Andrew Dunstan
-
- 07 2月, 2004 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 04 2月, 2004 1 次提交
-
-
由 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.
-
- 29 1月, 2004 1 次提交
-
-
由 Tom Lane 提交于
whereToSendOutput instead because they are really inquiring about the correct client communication protocol. Update some comments. This is pointing towards supporting regular FE/BE client protocol in a standalone backend, per discussion a month or so back.
-
- 27 1月, 2004 3 次提交
-
-
由 Bruce Momjian 提交于
PostmasterPid variable, which gets set (early) in PostmasterMain getppid would not be the postmaster? [fork/exec] Implements processCancelRequest by keeping an array of pid/cancel_key structs in shared mem [fork/exec] Moves AttachSharedMemoryAndSemaphores call for backends into SubPostmasterMain [win32] Implements reaper/waitpid by keeping an arrays of children pids,handles in postmaster local mem - this item is largely untested, for reasons which should be obvious, but appears sound [win32/all] Added extern for pgpipe in Win32 case, and changed the second pipe call (which seems to have been missed earlier) to pgpipe [win32] #define'd ftruncate to chsize in the Win32 case [win32] PG_USLEEP for Win32 has a misplaced paren. Fixed. [win32] DLLIMPORT handling for MingW case Claudio Natoli
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
apply. Alvaro Herrera
-
- 07 1月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
BackendFork/SSDataBase/pgstat) startup, to allow fork/exec calls to closely mimic (the soon to be provided) Win32 CreateProcess equivalent calls. Claudio Natoli
-
由 Neil Conway 提交于
backend.
-
- 25 12月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
fork/exec'd, in the same mode as the previous patch for backends. Claudio Natoli
-
- 21 12月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Claudio Natoli
-
- 02 12月, 2003 1 次提交
-
-
由 Tom Lane 提交于
on 64-bit Solaris. Use a non-system-dependent datatype for UsedShmemSegID, namely unsigned long (which we were already assuming could hold a shmem key anyway, cf RecordSharedMemoryInLockFile).
-
- 30 11月, 2003 2 次提交
-
-
由 Tom Lane 提交于
standalone backend --- the CVS revision number of postgres.c is not real useful to anyone.
-
由 PostgreSQL Daemon 提交于
$Header: -> $PostgreSQL Changes ...
-
- 24 11月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 20 10月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 19 10月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
machine readable, without headers, not sorted. Parameter descriptions adjusted to fit first sentence + rest convention.
-
- 17 10月, 2003 1 次提交
-
-
由 Tom Lane 提交于
protocol, per report from Igor Shevchenko. NOTIFY thought it could do its thing if transaction blockState is TBLOCK_DEFAULT, but in reality it had better check the low-level transaction state is TRANS_DEFAULT as well. Formerly it was not possible to wait for the client in a state where the first is true and the second is not ... but now we can have such a state. Minor cleanup in StartTransaction() as well.
-
- 09 10月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Have log_duration print when log_min_duration_statement prints.
-
- 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 次提交
-
-
由 Bruce Momjian 提交于
pointed out by Peter.
-
- 02 10月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
developed on -hackers.
-
- 30 9月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
this query?" logic in postgres.c Also, make it print "duration:" like log_duration. Neil Conway
-
- 29 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 27 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
every string, especially if some of the output should be fixed-format machine-readable. This needs to be more carefully sorted out. Also, make the help message generated by --help-config -h be more similar in style to the others.
-
- 25 9月, 2003 2 次提交
-
-
由 Peter Eisentraut 提交于
terms, add some clarifications, fix some untranslatable attempts at dynamic message building.
-
由 Tom Lane 提交于
now able to cope with assigning new relfilenode values to nailed-in-cache indexes, so they can be reindexed using the fully crash-safe method. This leaves only shared system indexes as special cases. Remove the 'index deactivation' code, since it provides no useful protection in the shared- index case. Require reindexing of shared indexes to be done in standalone mode, but remove other restrictions on REINDEX. -P (IgnoreSystemIndexes) now prevents using indexes for lookups, but does not disable index updates. It is therefore safe to allow from PGOPTIONS. Upshot: reindexing system catalogs can be done without a standalone backend for all cases except shared catalogs.
-
- 14 9月, 2003 1 次提交
-
-
由 Tom Lane 提交于
not before, to avoid duplication of effort.
-
- 03 9月, 2003 1 次提交
-
-
由 Tom Lane 提交于
config file if it exists. This was already discussed as being a good idea, and now seems the cleanest way to deal with initdb-time failures on machines with small SHMMAX. (The submitted patches instead modified initdb.sh to pass the correct sizing parameters, but that would still leave standalone backends prone to failure later. An admin who needs to use a standalone backend has enough trouble already, he shouldn't have to manually configure its shmem settings...)
-
- 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.
-
- 14 8月, 2003 1 次提交
-
-
由 Tom Lane 提交于
just before CommitTransactionCommand(). This is a more sensible place to put it since commit discards a lot of contexts, and we'd not find out about stomps affecting only transaction-local contexts.
-