- 06 3月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
o Change all current CVS messages of NOTICE to WARNING. We were going to do this just before 7.3 beta but it has to be done now, as you will see below. o Change current INFO messages that should be controlled by client_min_messages to NOTICE. o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc. to always go to the client. o Remove INFO from the client_min_messages options and add NOTICE. Seems we do need three non-ERROR elog levels to handle the various behaviors we need for these messages. Regression passed.
-
- 03 3月, 2002 1 次提交
-
-
由 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
-
- 12 1月, 2002 1 次提交
-
-
由 Tom Lane 提交于
FrozenTransactionId, not the XID of the creating transaction. Without this it's possible for a reference to a long-gone CLOG record to occur, per Christian Meunier's bug report of 10-Jan-02. Worse, the sequence tuple would become invisible to SELECTs after 2 billion transactions. Since the fix is applied during sequence creation it does not help existing databases, unless you drop and recreate every sequence. However, we intend to force initdb for 7.2RC1 anyway, to fix a pg_proc error, so I see no need to do more for this problem.
-
- 06 11月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
initdb/regression tests pass.
-
- 28 10月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
spacing. Also adds space for one-line comments.
-
- 25 10月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
tests pass.
-
- 19 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 17 8月, 2001 1 次提交
-
-
由 Tom Lane 提交于
has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
-
- 11 8月, 2001 1 次提交
-
-
由 Tom Lane 提交于
default, but OIDS are removed from many system catalogs that don't need them. Some interesting side effects: TOAST pointers are 20 bytes not 32 now; pg_description has a three-column key instead of one. Bugs fixed in passing: BINARY cursors work again; pg_class.relhaspkey has some usefulness; pg_dump dumps comments on indexes, rules, and triggers in a valid order. initdb forced.
-
- 30 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
stub) into the rest of the system. Adopt a cleaner approach to preventing deadlock in concurrent heap_updates: allow RelationGetBufferForTuple to select any page of the rel, and put the onus on it to lock both buffers in a consistent order. Remove no-longer-needed isExtend hack from API of ReleaseAndReadBuffer.
-
- 23 6月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
sequence.
-
- 14 6月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
Marko Kreen
-
- 07 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
create sequence a1234567890123456789012345678901234567890; select nextval('a1234567890123456789012345678901234567890');
-
- 02 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 27 5月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
privileges. INSERT and COPY FROM now require INSERT (only). Add privileges regression test.
-
- 11 5月, 2001 1 次提交
-
-
由 Tom Lane 提交于
not being consulted anywhere, so remove it and remove the _mdnblocks() calls that were used to set it. Change smgrextend interface to pass in the target block number (ie, current file length) --- the caller always knows this already, having already done smgrnblocks(), so it's silly to do it over again inside mdextend. Net result: extension of a file now takes one lseek(SEEK_END) and a write(), not three lseeks and a write.
-
- 04 4月, 2001 2 次提交
-
-
由 Vadim B. Mikheev 提交于
Thanks to Tom.
-
由 Vadim B. Mikheev 提交于
-
- 22 3月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 3月, 2001 1 次提交
-
-
由 Tom Lane 提交于
succeeds or not. Revise rtree page split algorithm to take care about making a feasible split --- ie, will the incoming tuple actually fit? Failure to make a feasible split, combined with failure to notice the failure, account for Jim Stone's recent bug report. I suspect that hash and gist indices may have the same type of bug, but at least now we'll get error messages rather than silent failures if so. Also clean up rtree code to use Datum rather than char* where appropriate.
-
- 13 2月, 2001 1 次提交
-
-
由 Philip Warner 提交于
-
- 25 1月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 13 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
are now critical sections, so as to ensure die() won't interrupt us while we are munging shared-memory data structures. Avoid insecure intermediate states in some code that proc_exit will call, like palloc/pfree. Rename START/END_CRIT_CODE to START/END_CRIT_SECTION, since that seems to be what people tend to call them anyway, and make them be called with () like a function call, in hopes of not confusing pg_indent. I doubt that this is sufficient to make SIGTERM safe anywhere; there's just too much code that could get invoked during proc_exit().
-
- 28 12月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 09 12月, 2000 2 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
value greater than one. The behavior this sought to disallow doesn't seem any less confusing than the other behaviors of cached sequences. Improve wording of some error messages, too. Update documentation accordingly. Also add an explanation that aborted transactions do not roll back their nextval() calls; this seems to be a FAQ, so it ought to be mentioned here...
-
- 04 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
values, whether the local char type is signed or not. This is necessary for portability. Per discussion on pghackers around 9/16/00.
-
- 03 12月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
critical sections of code.
-
- 30 11月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
CommitDelay in guc.c
-
- 17 10月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 15 10月, 2000 1 次提交
-
-
由 Philip Warner 提交于
-
- 11 10月, 2000 1 次提交
-
-
由 Philip Warner 提交于
(will be used in a future pg_dump).
-
- 06 9月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
user is now defined in terms of the user id, the user name is only computed upon request (for display purposes). This is kind of the opposite of the previous state, which would maintain the user name and compute the user id for permission checks. Besides perhaps saving a few cycles (integer vs string), this now creates a single point of attack for changing the user id during a connection, for purposes of "setuid" functions, etc.
-
- 04 8月, 2000 1 次提交
-
-
由 Tom Lane 提交于
We're reaching the mopup stage here (good thing too, this is getting tedious).
-
- 06 7月, 2000 1 次提交
-
-
由 Tom Lane 提交于
one of updating the whole text datatype, but there are so dang many calls of these two routines that it seems worth a separate commit.
-
- 15 6月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
we'll get there one day. Use `cat' to create aclocal.m4, not `aclocal'. Some people don't have automake installed. Only run the autoconf rule in the top-level GNUmakefile if the invoker specified `make configure', don't run it automatically because of CVS timestamp skew.
-
- 12 6月, 2000 1 次提交
-
-
由 Tom Lane 提交于
quote-stripping, and acl-checking tasks for these functions from the parser, and do them at function execution time instead. This fixes the failure of pg_dump to produce correct output for nextval(Foo) used in a rule, and also eliminates the restriction that the argument of these functions must be a parse-time constant.
-
- 13 4月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 15 1月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 31 12月, 1999 1 次提交
-
-
由 Tom Lane 提交于
sequence doesn't exist.
-