- 14 3月, 2001 6 次提交
-
-
由 Tom Lane 提交于
Could do with more testing, but it works in the simple cases.
-
由 Peter Eisentraut 提交于
pg_ctl '-l' option.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
detect case that next page in log came from an older run than the prior page. This avoids the necessity to re-zero the log after recovery from a crash, which is good because we need not risk destroying valuable log information. This forces another initdb since yesterday :-(. Need to get that log reset utility done...
-
由 Peter Eisentraut 提交于
-
- 13 3月, 2001 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Philip Warner 提交于
- Large Object dumps - Compressed custom format - Requirement to use template0 when creating DB
-
由 Philip Warner 提交于
- Use exact table names when enabling/disabling triggers
-
由 Hiroshi Inoue 提交于
ODBC driver on Windows 9X/ME/NT/2K when using the later versions of the driver that don't have the Installshield installation: 1) Install psqlodbc.dll in to C:\Windows\System or C:\Winnt\System32 2) Add the registry settings in the attached file using regedit. A useful addition to src/interfaces/odbc perhaps? Regards, Dave.
-
由 Tom Lane 提交于
-
由 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.
-
由 Tom Lane 提交于
tuples inserted/deleted/updated in a single transaction. On my machine, this reduced the time to delete 80000 tuples in a foreign-key-referencing table from ~15min to ~8sec.
-
- 12 3月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 11 3月, 2001 9 次提交
-
-
由 Peter Eisentraut 提交于
AC_SUBST that messed up the diversions and thus the configure output.
-
由 Peter Eisentraut 提交于
Respect default port setting in JDBC driver. Pick up version number from Makefile.global. Change installation directory to share/java/. Document.
-
由 Tom Lane 提交于
driver does not work because its internal cross-references get bound to similarly named functions in unixODBC shared library.
-
由 Tom Lane 提交于
psqlodbc.c's constructor-making techniques do not work.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
of DSSSL.
-
- 10 3月, 2001 6 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
under the postmaster --- specifically, if we are a standalone backend running under the initdb script, this is critical!
-
由 Hiroshi Inoue 提交于
2)Fix some memory leaks. 3)Change some bogus error messages.
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
handle this.
-
由 Peter Eisentraut 提交于
-
- 09 3月, 2001 4 次提交
-
-
由 Hiroshi Inoue 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 08 3月, 2001 5 次提交
-
-
由 Tom Lane 提交于
be allowed to receive ungrouped variables of the current query level. Curious that no one reported this bug before...
-
由 Tom Lane 提交于
of a counted input string. Marinos Yannikos' recent crash report turns out to be due to applying pg_ascii2wchar_with_len to a TEXT object that is smack up against the end of memory. This is the second just-barely- reproducible bug report I have seen that traces to some bit of code fetching one more byte than it is allowed to. Let's be more careful out there, boys and girls. While at it, I changed the code to not risk a similar crash when there is a truncated multibyte character at the end of an input string. The output in this case might not be the most reasonable output possible; if anyone wants to improve it further, step right up...
-
由 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.
-
由 Bruce Momjian 提交于
One more :)) It's for improper function argumets for PLTCL_UNKNOWN_SUPPORT code I'm not an autoconf expert, but is it possible to enable unknown support in pltcl with configure option ? This support is really handy for real life usage of pl/tcl. seva@sevasoft.kiev.ua
-
由 Bruce Momjian 提交于
in splitting code: seva@sevasoft.kiev.ua
-
- 07 3月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
directories, per suggestion from Robert Creager.
-