- 04 3月, 2002 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
speed up repetitive failed searches; per pghackers discussion in late January. inval.c logic substantially simplified, since we can now treat inserts and deletes alike as far as inval events are concerned. Some repair work needed in heap_create_with_catalog, which turns out to have been doing CommandCounterIncrement at a point where the new relation has non-self-consistent catalog entries. With the new inval code, that resulted in assert failures during a relcache entry rebuild.
-
由 Bruce Momjian 提交于
-
- 03 3月, 2002 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
now just below FATAL in server_min_messages. Added more text to highlight ordering difference between it and client_min_messages. --------------------------------------------------------------------------- REALLYFATAL => PANIC STOP => PANIC New INFO level the prints to client by default New LOG level the prints to server log by default Cause VACUUM information to print only to the client NOTICE => INFO where purely information messages are sent DEBUG => LOG for purely server status messages DEBUG removed, kept as backward compatible DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1 added DebugLvl removed in favor of new DEBUG[1-5] symbols New server_min_messages GUC parameter with values: DEBUG[5-1], INFO, NOTICE, ERROR, LOG, FATAL, PANIC New client_min_messages GUC parameter with values: DEBUG[5-1], LOG, INFO, NOTICE, ERROR, FATAL, PANIC Server startup now logged with LOG instead of DEBUG Remove debug_level GUC parameter elog() numbers now start at 10 Add test to print error message if older elog() values are passed to elog() Bootstrap mode now has a -d that requires an argument, like postmaster
-
由 Tom Lane 提交于
profiling timer setting across fork(). The correct way to build a profilable backend on Linux is now gmake PROFILE="-pg -DLINUX_PROFILE"
-
- 02 3月, 2002 7 次提交
-
-
由 Tom Lane 提交于
postmaster won't accept the request anyway. (If your kernel can't be trusted, SSL will not help you.)
-
由 Tom Lane 提交于
bounds of 1, not the lower bound subscripts of the original slice. Per bug report from Andre Holzner, 1-Feb-02.
-
由 Peter Eisentraut 提交于
variables. New commands ALTER DATABASE ... SET and ALTER USER ... SET.
-
由 Peter Eisentraut 提交于
return NULL.
-
由 Tom Lane 提交于
mergeclause is which when extracting selectivity info.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
manual page; pointed out by IRC user.
-
- 01 3月, 2002 3 次提交
-
-
由 Hiroshi Inoue 提交于
-
由 Tom Lane 提交于
in RestrictInfo nodes, instead of recomputing on every use.
-
由 Tom Lane 提交于
both input streams to the end. If one variable's range is much less than the other, an indexscan-based merge can win by not scanning all of the other table. Per example from Reinhard Max.
-
- 28 2月, 2002 5 次提交
-
-
由 Tom Lane 提交于
before reporting command-complete message for the final command of a query string. This way, any errors detected during finish_xact_command (such as RI violations) will appear to be part of the final command, rather than coming out after the command is reported complete. This avoids confusing PQendcopy and other not-overly-bright clients. Per Lee Harr's bug report of 25-Feb-02.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
matches the sequence name from pg_class. This fails if the sequence has been renamed, and seems rather pointless in any case. Also improve a couple of error messages about inconsistencies.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
are now both invoked once per received SQL command (raw parsetree) from pg_exec_query_string. BeginCommand is actually just an empty routine at the moment --- all its former operations have been pushed into tuple receiver setup routines in printtup.c. This makes for a clean distinction between BeginCommand/EndCommand (once per command) and the tuple receiver setup/teardown routines (once per ExecutorRun call), whereas the old code was quite ad hoc. Along the way, clean up the calling conventions for ExecutorRun a little bit.
-
- 27 2月, 2002 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Hiroshi Inoue 提交于
Change SQLGetFunctions() to reply not yet implemented ODBC 3.0 functions precisely.
-
由 Tatsuo Ishii 提交于
See pgsql-bugs/pgsql-hackers discussion "COPY FROM is not 8bit clean" around 2002/02/26 for more details -- Tatsuo Ishii
-
由 Tom Lane 提交于
report for each received SQL command, regardless of rewriting activity. Also ensure that this report comes from the 'original' command, not the last command generated by rewrite; this fixes 7.2 breakage for INSERT commands that have actions added by rules. Fernando Nasser and Tom Lane.
-
- 26 2月, 2002 11 次提交
-
-
由 Tom Lane 提交于
-
由 Dave Cramer 提交于
-
由 Tom Lane 提交于
gripe from Dan Langille.
-
由 Tom Lane 提交于
names. This is a temporary measure to allow backwards compatibility with 7.2 and earlier pg_dump. 7.2.1 and later pg_dump will double-quote mixed case names in \connect. Once we feel that older dumps are not a problem anymore, we can revert this change and treat \connect arguments as normal SQL identifiers.
-
由 Bruce Momjian 提交于
> * Remove memory/file descriptor freeing befor elog(ERROR) (Bruce)
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> and that the right fix is to make each of the subsequent calls be in > this same pattern, not to try to emulate their nonsensical style. Dominic J. Eidson
-
由 Bruce Momjian 提交于
> o Add LISTEN/NOTIFY support to the JDBC driver (Barry) 479a481 > * Barry is Barry Lind <barry@xythos.com> 482a485 > * Dave is Dave Cramer <dave@fastcrypt.com>
-
由 Tom Lane 提交于
-
由 Thomas G. Lockhart 提交于
Fix a few apparently-wrong TZ vs DTZ declarations.
-
- 25 2月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
> * -Prevent SIGHUP and 'pg_ctl reload' from changing command line > * -Remove LIMIT #,# and force use LIMIT and OFFSET clauses in 7.3 (Bruce) > * -Prevent create/drop scripts from allowing extra args (Bruce) > * -Have pg_dump -C dump database location and encoding information
-
由 Bruce Momjian 提交于
by making the static variables extra_before and extra_after automatic so we can use recursion. It gets much easier to generate extra commands now, and one can rest assured that the extra commands will be properly analyzed/rewritten. Without this patch, if a command produced by transformation tries to use these static lists their first contents would be lost with unpredictable results. I know I could fix this by just using nconc() instead of assignments, but the resulting order of the commands would not be exactly what one could expect. -- Fernando Nasser
-