- 14 3月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
This connection has been terminated by the administrator
-
- 13 3月, 2001 1 次提交
-
-
由 Tom Lane 提交于
* Store two past checkpoint locations, not just one, in pg_control. On startup, we fall back to the older checkpoint if the newer one is unreadable. Also, a physical copy of the newest checkpoint record is kept in pg_control for possible use in disaster recovery (ie, complete loss of pg_xlog). Also add a version number for pg_control itself. Remove archdir from pg_control; it ought to be a GUC parameter, not a special case (not that it's implemented yet anyway). * Suppress successive checkpoint records when nothing has been entered in the WAL log since the last one. This is not so much to avoid I/O as to make it actually useful to keep track of the last two checkpoints. If the things are right next to each other then there's not a lot of redundancy gained... * Change CRC scheme to a true 64-bit CRC, not a pair of 32-bit CRCs on alternate bytes. Polynomial borrowed from ECMA DLT1 standard. * Fix XLOG record length handling so that it will work at BLCKSZ = 32k. * Change XID allocation to work more like OID allocation. (This is of dubious necessity, but I think it's a good idea anyway.) * Fix a number of minor bugs, such as off-by-one logic for XLOG file wraparound at the 4 gig mark. * Add documentation and clean up some coding infelicities; move file format declarations out to include files where planned contrib utilities can get at them. * Checkpoint will now occur every CHECKPOINT_SEGMENTS log segments or every CHECKPOINT_TIMEOUT seconds, whichever comes first. It is also possible to force a checkpoint by sending SIGUSR1 to the postmaster (undocumented feature...) * Defend against kill -9 postmaster by storing shmem block's key and ID in postmaster.pid lockfile, and checking at startup to ensure that no processes are still connected to old shmem block (if it still exists). * Switch backends to accept SIGQUIT rather than SIGUSR1 for emergency stop, for symmetry with postmaster and xlog utilities. Clean up signal handling in bootstrap.c so that xlog utilities launched by postmaster will react to signals better. * Standalone bootstrap now grabs lockfile in target directory, as added insurance against running it in parallel with live postmaster.
-
- 09 3月, 2001 1 次提交
-
-
由 Hiroshi Inoue 提交于
-
- 24 2月, 2001 1 次提交
-
-
由 Tom Lane 提交于
proc_exit(1). Unless you think a system-wide restart is an appropriate response to bogus PGOPTIONS, that is.
-
- 18 2月, 2001 1 次提交
-
-
由 Tom Lane 提交于
either wrong or unnecessary in most cases, and on systems where setting status takes a kernel call, the overhead of setting status three times per command rather than two is annoying.
-
- 25 1月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 24 1月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 20 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
into distinct concepts, per recent discussion on pghackers.
-
- 17 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 14 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
are treated more like 'cancel' interrupts: the signal handler sets a flag that is examined at well-defined spots, rather than trying to cope with an interrupt that might happen anywhere. See pghackers discussion of 1/12/01.
-
- 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().
-
- 07 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
of 6 Jan 2001 21:55.
-
- 21 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
observed by Inoue. Also, don't call ProcRemove() from postmaster if we have detected a backend crash --- too risky if shared memory is corrupted. It's not needed anyway, considering we are going to reinitialize shared memory and semaphores as soon as the last child is dead.
-
- 19 12月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
>> xlog.c : special case for beos to avoid 'link' which does not work yet >> beos/sem.c : implementation of new sem_ctl call (GETPID) and a new >sem_op >> flag (IPCNOWAIT) >> dynloader/beos.c : add a verification of symbol validity (seem that the >> loader sometime return OK with an invalid symbol) >> postmaster.c : add beos forking support for the new checkpoint process >> postgres.c : remove beos special case for getrusage >> beos.h : Correction of a bas definition of AF_UNIX, misc defnitions >> >> >> thanks >> >> >> cyril Cyril VELTER
-
由 Tom Lane 提交于
might change it. Experimentation shows that the signal handler call mechanism does not save/restore errno for you, at least not on Linux or HPUX, so this is definitely a real risk.
-
- 18 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
to ensure that we have released buffer refcounts and so forth, rather than putting ad-hoc operations before (some of the calls to) proc_exit. Add commentary to discourage future hackers from repeating that mistake.
-
- 03 12月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
critical sections of code.
-
- 30 11月, 2000 2 次提交
-
-
由 Vadim B. Mikheev 提交于
SetConfigOption(name, value, (IsUnderPostmaster) ? PGC_BACKEND : PGC_POSTMASTER);
-
由 Tom Lane 提交于
socket file, in favor of having an ordinary lockfile beside the socket file. Clean up a few robustness problems in the lockfile code. If postmaster is going to reject a connection request based on database state, it will now tell you so before authentication exchange not after. (Of course, a failure after is still possible if conditions change meanwhile, but this makes life easier for a yet-to-be-written pg_ping utility.)
-
- 26 11月, 2000 2 次提交
-
-
由 Tom Lane 提交于
re-adopt these settings at every postmaster or standalone-backend startup. This should fix problems with indexes becoming corrupt due to failure to provide consistent locale environment for postmaster at all times. Also, refuse to start up a non-locale-enabled compilation in a database originally initdb'd with a non-C locale. Suppress LIKE index optimization if locale is not "C" or "POSIX" (are there any other locales where it's safe?). Issue NOTICE during initdb if selected locale disables LIKE optimization.
-
由 Peter Eisentraut 提交于
Accept --help even if no general long options support exists.
-
- 22 11月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 15 11月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 09 11月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 07 11月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
to work everywhere. Also, on FreeBSD you need to set the optreset variable to 1 before parsing the command line a second time with getopt().
-
- 04 11月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
it to an absolute path.
-
- 29 10月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 28 10月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 27 10月, 2000 1 次提交
-
-
由 Tom Lane 提交于
Sorry 'bout that, chief...
-
- 25 10月, 2000 1 次提交
-
-
由 Tom Lane 提交于
for input, not just before.
-
- 07 10月, 2000 3 次提交
-
-
由 Bruce Momjian 提交于
after that dynamic loading isn't working and shared memory handling is broken. Attached with this message, there is a Zip file which contain : * beos.diff = patch file generated with difforig * beos = folder with beos support files which need to be moved in / src/backend/port * expected = foler with three file for message and precision difference in regression test * regression.diff = rule problem (need to kill the backend manualy) * dynloader = dynloader files (they are also in the pacth files, but there is so much modification that I have join full files) Everything works except a problem in 'rules' Is there some problems with rules in the current tree ? It used to works with last week tree. Cyril VELTER
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
took some rejiggering of typename and ACL parsing, as well as moving parse_analyze call out of parser(). Restructure postgres.c processing so that parse analysis and rewrite are skipped when in abort-transaction state. Only COMMIT and ABORT statements will be processed beyond the raw parser() phase. This addresses problem of parser failing with database access errors while in aborted state (see pghackers discussions around 7/28/00). Also fix some bugs with COMMIT/ABORT statements appearing in the middle of a single query input string. Function, operator, and aggregate arguments/results can now use full TypeName production, in particular foo[] for array types. DROP OPERATOR and COMMENT ON OPERATOR were broken for unary operators. Allow CREATE AGGREGATE to accept unquoted numeric constants for initcond.
-
- 03 10月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
working on the VERY latest version of BeOS. I'm sure there will be alot of comments, but then if there weren't I'd be disappointed! Thanks for your continuing efforts to get this into your tree. Haven't bothered with the new files as they haven't changed. BTW Peter, the compiler is "broken" about the bool define and so on. I'm filing a bug report to try and get it addressed. Hopefully then we can tidy up the code a bit. I await the replies with interest :) David Reid
-
由 Peter Eisentraut 提交于
-
- 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.
-
- 31 8月, 2000 1 次提交
-
-
由 Tom Lane 提交于
resources are cleaned up if the user disconnected mid-transaction. Great thanks to Hiroshi for pointing out what should have been obvious...
-
- 29 8月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 28 8月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
the harm potential outweighs the possible benefits.
-