hcq/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2026-04-10 12:47:01 +08:00
Code Issues Packages Projects Releases Wiki Activity

Commit Graph

  • 3cd318a8d1 Fix gratuitous message spelling differences Peter Eisentraut 2006-11-27 15:50:55 +00:00
  • 81b0b06462 Make pg_restore usage examples more useful: illustrate restoring into both the same database name and a different one. Tom Lane 2006-11-26 18:11:11 +00:00
  • 50271fc9b3 Fix misspellings of GB. Peter Eisentraut 2006-11-25 22:55:59 +00:00
  • 818ac8479b Correct misspellings of kB. Peter Eisentraut 2006-11-25 22:44:48 +00:00
  • b12add99c2 Cosmetic release note fix. Neil Conway 2006-11-25 07:03:57 +00:00
  • c11b5228cf update for rc1 REL8_2_RC1 PostgreSQL Daemon 2006-11-25 03:34:13 +00:00
  • 0d9e0d9dde Copy fsync() defines into test_fsync.c, someday place them in an include. Bruce Momjian 2006-11-25 01:22:28 +00:00
  • f14d43d2d3 Document that to_char() "TM" is controlled by lc_messages. Bruce Momjian 2006-11-25 00:38:53 +00:00
  • a7a3d0f0d9 Update release notes for RC1. Tom Lane 2006-11-24 23:31:55 +00:00
  • e53a43bf17 Fix psql's \copy command to ensure that it cycles libpq back to the idle state (in particular, causing the ReadyForQuery message to be eaten) before returning from do_copy. The only known consequence of failing to do so is that get_prompt might show a wrong result for the %x transaction status escape, as reported by Bernd Helmle; but it's possible there are other issues. Tom Lane 2006-11-24 23:07:07 +00:00
  • fc821135fb Fix psql's \copy command to ensure that it cycles libpq back to the idle state (in particular, causing the ReadyForQuery message to be eaten) before returning from do_copy. The only known consequence of failing to do so is that get_prompt might show a wrong result for the %x transaction status escape, as reported by Bernd Helmle; but it's possible there are other issues. Tom Lane 2006-11-24 23:07:01 +00:00
  • 2f523a6f53 Fix psql's \copy command to ensure that it cycles libpq back to the idle state (in particular, causing the ReadyForQuery message to be eaten) before returning from do_copy. The only known consequence of failing to do so is that get_prompt might show a wrong result for the %x transaction status escape, as reported by Bernd Helmle; but it's possible there are other issues. Tom Lane 2006-11-24 23:06:56 +00:00
  • df3a6fe477 Fix psql's \copy command to ensure that it cycles libpq back to the idle state (in particular, causing the ReadyForQuery message to be eaten) before returning from do_copy. The only known consequence of failing to do so is that get_prompt might show a wrong result for the %x transaction status escape, as reported by Bernd Helmle; but it's possible there are other issues. Tom Lane 2006-11-24 23:06:50 +00:00
  • 9b15b14014 Revert (too late in beta): Bruce Momjian 2006-11-24 22:25:56 +00:00
  • 988a87a03a Change pg_stat_all_tables and sister views to put the recently-added vacuum/analyze timestamp columns at the end, rather than at a random spot in the middle as in the original patch. This was deemed more usable as well as less likely to break existing application code. initdb forced accordingly. In passing, remove former kluge for initializing pg_stat_file()'s pg_proc entry --- bootstrap mode was fixed recently so that this can be done without any hacks, but I overlooked this usage. Tom Lane 2006-11-24 21:18:42 +00:00
  • 2822c7c0fc Make contrib/isn pass the opr_sanity sanity checks: add missing commutator operators, and mark hash-opclass members as oprcanhash. This is a pretty ugly, brute-force solution, but it seems that getting rid of all these redundant-looking operators would require some tweaks in the core operator-resolution code to behave nicely, and I'm not willing to risk that just before RC1. Tom Lane 2006-11-24 18:44:37 +00:00
  • 2c82df2a06 Translation updates Peter Eisentraut 2006-11-24 17:11:57 +00:00
  • 8c1ce4559d Separate release preparation jobs for all releases and for major releases Peter Eisentraut 2006-11-24 17:03:50 +00:00
  • d2b694d825 Fix to_char() locale handling to honor LC_TIME, not LC_MESSAGES. Bruce Momjian 2006-11-24 15:26:18 +00:00
  • 409600942b KB -> kB Peter Eisentraut 2006-11-24 09:20:12 +00:00
  • 3de2682a1e Fix lowercasing while parse OO dictionary Teodor Sigaev 2006-11-23 17:35:14 +00:00
  • 1120c61b29 Revert out: Bruce Momjian 2006-11-23 17:20:47 +00:00
  • 3455b0a5d5 Update fsync test to match new O_DIRECT behavior. Bruce Momjian 2006-11-23 16:41:11 +00:00
  • eb1fbbe5c4 Update wording: > * Add a field 'isoyear' to extract(), based on the ISO week Bruce Momjian 2006-11-23 16:18:12 +00:00
  • 28568e585f Spelling and related minor fixes for the GIN docs. Neil Conway 2006-11-23 05:58:01 +00:00
  • ce3d1a4fbc Un-break ecpg regression test. Tom Lane 2006-11-23 05:47:48 +00:00
  • 34036c8658 More minor SGML improvements for xfunc.sgml, including making some titles more concise. (We usually don't need to repeat the name of a section in the title of one of its subsections.) Neil Conway 2006-11-23 05:43:32 +00:00
  • ebf071643a Document that Kerberos is for authentication, and does not encrypt data or queries over the network. Bruce Momjian 2006-11-23 05:39:17 +00:00
  • 4ed6f6d479 Fix a typo in recent xfunc addition, do some routine SGML police work. Neil Conway 2006-11-23 05:28:18 +00:00
  • 546d6848ca Add a comment noting that heap_copytuple_with_tuple() results in a HeapTuple that is no longer allocated as a single palloc() block; if used carelessly, this might result in a subsequent memory leak after heap_freetuple(). Neil Conway 2006-11-23 05:27:18 +00:00
  • 0c6f167c4a Update lock comments for concurrent index creation, analyze. Bruce Momjian 2006-11-23 05:14:04 +00:00
  • 3bd2e3e92b Add: Bruce Momjian 2006-11-23 05:09:26 +00:00
  • cb21b9fc13 Add: Bruce Momjian 2006-11-23 05:01:47 +00:00
  • 956c2d6683 Make ecpg test variable 'times' static so as not to conflict with libc symbol. Bruce Momjian 2006-11-23 04:38:01 +00:00
  • ab79444e7b Add "(assuming <varname>standard_conforming_strings</> is <literal>off</>)" clauses for bytea. Bruce Momjian 2006-11-23 04:27:33 +00:00
  • 5f78aa5acf Shared Memory Hooks Documentation Bruce Momjian 2006-11-23 03:52:05 +00:00
  • 35f9bf3725 Add release entry for 8.1.5 that was missing: Bruce Momjian 2006-11-23 03:31:04 +00:00
  • 3e0c96b2ec Add release entry for 8.1.5 that was missing: Bruce Momjian 2006-11-23 03:30:49 +00:00
  • 395249ecbe Several changes to reduce the probability of running out of memory during AbortTransaction, which would lead to recursion and eventual PANIC exit as illustrated in recent report from Jeff Davis. First, in xact.c create a special dedicated memory context for AbortTransaction to run in. This solves the problem as long as AbortTransaction doesn't need more than 32K (or whatever other size we create the context with). But in corner cases it might. Second, in trigger.c arrange to keep pending after-trigger event records in separate contexts that can be freed near the beginning of AbortTransaction, rather than having them persist until CleanupTransaction as before. Third, in portalmem.c arrange to free executor state data earlier as well. These two changes should result in backing off the out-of-memory condition before AbortTransaction needs any significant amount of memory, at least in typical cases such as memory overrun due to too many trigger events or too big an executor hash table. And all the same for subtransaction abort too, of course. Tom Lane 2006-11-23 01:14:59 +00:00
  • 0951ff33b5 Fix 1-byte buffer overrun when OID exceeds 1 billion. This probably can't cause any serious harm in normal cases, but if you have gcc buffer overrun checking turned on, that will notice. Found by Jack Orenstein. Problem was already fixed in CVS HEAD. Tom Lane 2006-11-22 21:13:16 +00:00
  • 8637cd1ee8 Fix 1-byte buffer overrun when OID exceeds 1 billion. This probably can't cause any serious harm in normal cases, but if you have gcc buffer overrun checking turned on, that will notice. Found by Jack Orenstein. Problem was already fixed in CVS HEAD. Tom Lane 2006-11-22 21:13:11 +00:00
  • db8a3fd680 Fix 1-byte buffer overrun when OID exceeds 1 billion. This probably can't cause any serious harm in normal cases, but if you have gcc buffer overrun checking turned on, that will notice. Found by Jack Orenstein. Problem was already fixed in CVS HEAD. Tom Lane 2006-11-22 21:13:04 +00:00
  • c4950aa1ee Fix 1-byte buffer overrun when OID exceeds 1 billion. This probably can't cause any serious harm in normal cases, but if you have gcc buffer overrun checking turned on, that will notice. Found by Jack Orenstein. Problem was already fixed in CVS HEAD. Tom Lane 2006-11-22 21:12:57 +00:00
  • 2a55984162 More HA wording improvements. Bruce Momjian 2006-11-22 18:15:34 +00:00
  • b035722f29 Update HA docs with more wording improvements. Bruce Momjian 2006-11-22 18:14:26 +00:00
  • 6346355a9b Wording and term clarification for HA docs, per Markus Schiltknecht. Bruce Momjian 2006-11-22 17:36:52 +00:00
  • 84151d0644 Avoid infinity calculations in rank_cd Teodor Sigaev 2006-11-22 15:55:05 +00:00
  • ba2edcac4f Mention OIDs are now not created by default. Bruce Momjian 2006-11-22 04:17:03 +00:00
  • 8c556ce1c2 New async/sync multi-master headings for docs. Bruce Momjian 2006-11-22 04:01:40 +00:00
  • 3b0313580e New async/sync multi-master headings for docs. Bruce Momjian 2006-11-22 04:00:19 +00:00
  • ffa0e8f0cd Add mention of shared-memory/disk for multi-master clustering. Bruce Momjian 2006-11-22 03:44:52 +00:00
  • 617f123f06 Get rid of retail definitions of HAVE_STRDUP and HAVE_VSNPRINTF in some of the Windows-only makefiles; the correct place to assert these things is pg_config.h.win32. Per bug #2677. Tom Lane 2006-11-21 23:26:47 +00:00
  • d735804f88 Translate Windows' GMT Standard Time/GMT Daylight Time zones to zic's Europe/London, rather than Europe/Dublin as before. This seems a less surprising choice, particularly with respect to dates before 1948. Original suggestion was to translate to straight GMT, but this seems wrong given that these zones *are* DST-aware. Per offlist discussion with Magnus. Tom Lane 2006-11-21 23:11:55 +00:00
  • 188b744d95 HA doc wording improvement. Bruce Momjian 2006-11-21 22:48:33 +00:00
  • 7ec1c5a867 Prevent intratransaction memory leak when a subtransaction is aborted in the middle of executing a SPI query. This doesn't entirely fix the problem of memory leakage in plpgsql exception handling, but it should get rid of the lion's share of leakage. Tom Lane 2006-11-21 22:35:29 +00:00
  • 5fc2d7e451 Suppress timezone (%Z) part of timestamp display when running on Windows, because on that platform strftime produces localized zone names in varying encodings. Even though it's only in a comment, this can cause encoding errors when reloading the dump script. Per suggestion from Andreas Seltenreich. Also, suppress %Z on Windows in the %s escape of log_line_prefix ... not sure why this one is different from the other two, but it shouldn't be. Tom Lane 2006-11-21 22:19:46 +00:00
  • c714e5cba7 Fix plpython to work (or at least pass its regression tests) with python 2.5. This involves fixing several violations of the published spec for creating PyTypeObjects, and adding another regression test expected output for yet another variation of error message spelling. Tom Lane 2006-11-21 21:51:05 +00:00
  • a48e92ea1d Mention pgpool-II can do Clustering For Parallel Query Execution. Bruce Momjian 2006-11-21 21:37:33 +00:00
  • 3ad0728c81 On systems that have setsid(2) (which should be just about everything except Windows), arrange for each postmaster child process to be its own process group leader, and deliver signals SIGINT, SIGTERM, SIGQUIT to the whole process group not only the direct child process. This provides saner behavior for archive and recovery scripts; in particular, it's possible to shut down a warm-standby recovery server using "pg_ctl stop -m immediate", since delivery of SIGQUIT to the startup subprocess will result in killing the waiting recovery_command. Also, this makes Query Cancel and statement_timeout apply to scripts being run from backends via system(). (There is no support in the core backend for that, but it's widely done using untrusted PLs.) Per gripe from Stephen Harris and subsequent discussion. Tom Lane 2006-11-21 20:59:53 +00:00
  • de597154a8 Update Statement-Based Replication Middleware docs to be more general. Bruce Momjian 2006-11-21 18:31:57 +00:00
  • dd92a8c33f Fix type in return value Teodor Sigaev 2006-11-21 18:31:28 +00:00
  • ca646f66f7 In HA/load balancing does: Bruce Momjian 2006-11-21 18:15:45 +00:00
  • 66eda1c7b3 VC build patch from Magnus: Neil Conway 2006-11-21 17:54:26 +00:00
  • ae81a6329d Move libpq environment reference in psql documentation to a more appropriate place, per Andrew Dunstan. Bruce Momjian 2006-11-21 17:01:58 +00:00
  • f87fcd43c6 remove duplicate declaration, per report from Magnus Hagander. Andrew Dunstan 2006-11-21 16:59:02 +00:00
  • bcd713a618 If SSL negotiation fails and SSLMODE is 'prefer', then retry without SSL. Negotiation failure is only likely to happen if one side or the other is misconfigured, eg. bad client certificate. I'm not 100% convinced that a retry is really the best thing, hence not back-patching this fix for now. Per gripe from Sergio Cinos. Tom Lane 2006-11-21 16:28:00 +00:00
  • cc6c10a7a0 Add capitalization mention. Bruce Momjian 2006-11-21 15:38:09 +00:00
  • 150328cd61 I noticed that the Partitioning section of the docs has *two* sections of caveats in different places, but close together. One called caveats, one not. That looks like it just led to somebody not reading some appropriate caveats in the second group of caveats (on -admin). Bruce Momjian 2006-11-21 03:44:55 +00:00
  • 414c7a537e Change the default setting for log_min_error_statement to ERROR. Per recent discussion in which majority opinion was that this is a more widely useful setting than the previous default of PANIC. Tom Lane 2006-11-21 01:23:37 +00:00
  • e82d9e6283 Adjust elog.c so that elog(FATAL) exits (including cases where ERROR is promoted to FATAL) end in exit(1) not exit(0). Then change the postmaster to allow exit(1) without a system-wide panic, but not for the startup subprocess or the bgwriter. There were a couple of places that were using exit(1) to deliberately force a system-wide panic; adjust these to be exit(2) instead. This fixes the problem noted back in July that if the startup process exits with elog(ERROR), the postmaster would think everything is hunky-dory and proceed to start up. Alternative solutions such as trying to run the entire startup process as a critical section seem less clean, primarily because of the fact that a fair amount of startup code is shared by all postmaster children in the EXEC_BACKEND case. We'd need an ugly special case somewhere near the head of main.c to make it work if it's the child process's responsibility to determine what happens; and what's the point when the postmaster already treats different children differently? Tom Lane 2006-11-21 00:49:55 +00:00
  • 778bb7b60d Retitle documentation section, "Statement-Based Replication Using Middleware". Bruce Momjian 2006-11-20 22:07:56 +00:00
  • b8c01d9dac Add mention that Shared Disk Failover can use file system mirroring of the mirroring is consistent. Bruce Momjian 2006-11-20 21:26:22 +00:00
  • fb2619859c Update Brazilian FAQ. Bruce Momjian 2006-11-20 20:58:40 +00:00
  • 016e0b4177 For to_char() day/month abbrevitions, mention "3 chars in English, localized lengths vary". Bruce Momjian 2006-11-20 20:20:18 +00:00
  • f88fff1e61 Our MingW FAQ appears to be seriously out of date. Couple of fixes: we want to direct MSI downloads to main download site, NT4 not supported anymore, msvc build env in progress, pgsql-hackers-win32 is no more. Bruce Momjian 2006-11-20 19:31:27 +00:00
  • aaef29b377 More MSVC build fixes: Tom Lane 2006-11-20 19:18:02 +00:00
  • e2b1dbd394 Overhaul the "External Projects" chapter in the manual. Replace the variabelist with a more concise table, add a URL for each project, remove some orphaned projects, add PL/Py, and various other changes. Initial patch from Robert Treat, subsequent work by Neil Conway. Neil Conway 2006-11-20 17:42:16 +00:00
  • 900c9962f7 Update documentation to use Statement-Based Replication rather than Query Broadcast. Bruce Momjian 2006-11-20 15:07:13 +00:00
  • 419fe7cd1b Fix bug http://archives.postgresql.org/pgsql-bugs/2006-10/msg00258.php. Fix string's length calculation for recoding, fix strlower() to avoid wrong assumption about length of recoded string (was: recoded string is no greater that source, it may not true for multibyte encodings) Thanks to Thomas H. <me@alternize.com> and Magnus Hagander <mha@sollentuna.net> Teodor Sigaev 2006-11-20 14:03:30 +00:00
  • b8222e5006 When truncating a relation in-place (eg during VACUUM), do not try to unlink any no-longer-needed segments; just truncate them to zero bytes and leave the files in place for possible future re-use. This avoids problems when the segments are re-used due to relation growth shortly after truncation. Before, the bgwriter, and possibly other backends, could still be holding open file references to the old segment files, and would write dirty blocks into those files where they'd disappear from the view of other processes. Tom Lane 2006-11-20 01:08:10 +00:00
  • 504d87c7cd When truncating a relation in-place (eg during VACUUM), do not try to unlink any no-longer-needed segments; just truncate them to zero bytes and leave the files in place for possible future re-use. This avoids problems when the segments are re-used due to relation growth shortly after truncation. Before, the bgwriter, and possibly other backends, could still be holding open file references to the old segment files, and would write dirty blocks into those files where they'd disappear from the view of other processes. Tom Lane 2006-11-20 01:08:02 +00:00
  • 1a5c450f30 When truncating a relation in-place (eg during VACUUM), do not try to unlink any no-longer-needed segments; just truncate them to zero bytes and leave the files in place for possible future re-use. This avoids problems when the segments are re-used due to relation growth shortly after truncation. Before, the bgwriter, and possibly other backends, could still be holding open file references to the old segment files, and would write dirty blocks into those files where they'd disappear from the view of other processes. Tom Lane 2006-11-20 01:07:56 +00:00
  • ddefff7247 Repair problems with hash indexes that span multiple segments: the hash code's preference for filling pages out-of-order tends to confuse the sanity checks in md.c, as per report from Balazs Nagy in bug #2737. The fix is to ensure that the smgr-level code always has the same idea of the logical EOF as the hash index code does, by using ReadBuffer(P_NEW) where we are adding a single page to the end of the index, and using smgrextend() to reserve a large batch of pages when creating a new splitpoint. The patch is a bit ugly because it avoids making any changes in md.c, which seems the most prudent approach for a backpatchable beta-period fix. After 8.3 development opens, I'll take a look at a cleaner but more invasive patch, in particular getting rid of the now unnecessary hack to allow reading beyond EOF in mdread(). Tom Lane 2006-11-19 21:33:46 +00:00
  • 006284b2ef Repair problems with hash indexes that span multiple segments: the hash code's preference for filling pages out-of-order tends to confuse the sanity checks in md.c, as per report from Balazs Nagy in bug #2737. The fix is to ensure that the smgr-level code always has the same idea of the logical EOF as the hash index code does, by using ReadBuffer(P_NEW) where we are adding a single page to the end of the index, and using smgrextend() to reserve a large batch of pages when creating a new splitpoint. The patch is a bit ugly because it avoids making any changes in md.c, which seems the most prudent approach for a backpatchable beta-period fix. After 8.3 development opens, I'll take a look at a cleaner but more invasive patch, in particular getting rid of the now unnecessary hack to allow reading beyond EOF in mdread(). Tom Lane 2006-11-19 21:33:37 +00:00
  • dfb25d2863 Repair problems with hash indexes that span multiple segments: the hash code's preference for filling pages out-of-order tends to confuse the sanity checks in md.c, as per report from Balazs Nagy in bug #2737. The fix is to ensure that the smgr-level code always has the same idea of the logical EOF as the hash index code does, by using ReadBuffer(P_NEW) where we are adding a single page to the end of the index, and using smgrextend() to reserve a large batch of pages when creating a new splitpoint. The patch is a bit ugly because it avoids making any changes in md.c, which seems the most prudent approach for a backpatchable beta-period fix. After 8.3 development opens, I'll take a look at a cleaner but more invasive patch, in particular getting rid of the now unnecessary hack to allow reading beyond EOF in mdread(). Tom Lane 2006-11-19 21:33:29 +00:00
  • d68efb3f8d Repair problems with hash indexes that span multiple segments: the hash code's preference for filling pages out-of-order tends to confuse the sanity checks in md.c, as per report from Balazs Nagy in bug #2737. The fix is to ensure that the smgr-level code always has the same idea of the logical EOF as the hash index code does, by using ReadBuffer(P_NEW) where we are adding a single page to the end of the index, and using smgrextend() to reserve a large batch of pages when creating a new splitpoint. The patch is a bit ugly because it avoids making any changes in md.c, which seems the most prudent approach for a backpatchable beta-period fix. After 8.3 development opens, I'll take a look at a cleaner but more invasive patch, in particular getting rid of the now unnecessary hack to allow reading beyond EOF in mdread(). Tom Lane 2006-11-19 21:33:23 +00:00
  • fa3d622cb0 Clarify description of CIDR-address column of pg_hba.conf, to discourage people from trying notations like '10.6/16', which is accepted but does not mean what you probably think. Per example from Paul Forgey. Tom Lane 2006-11-17 23:25:17 +00:00
  • 91eb4895bb Repair two related errors in heap_lock_tuple: it was failing to recognize cases where we already hold the desired lock "indirectly", either via membership in a MultiXact or because the lock was originally taken by a different subtransaction of the current transaction. These cases must be accounted for to avoid needless deadlocks and/or inappropriate replacement of an exclusive lock with a shared lock. Per report from Clarence Gardner and subsequent investigation. Tom Lane 2006-11-17 18:00:25 +00:00
  • 4f335a3d7f Repair two related errors in heap_lock_tuple: it was failing to recognize cases where we already hold the desired lock "indirectly", either via membership in a MultiXact or because the lock was originally taken by a different subtransaction of the current transaction. These cases must be accounted for to avoid needless deadlocks and/or inappropriate replacement of an exclusive lock with a shared lock. Per report from Clarence Gardner and subsequent investigation. Tom Lane 2006-11-17 18:00:15 +00:00
  • b6b5aa102b Small message equalization fix Peter Eisentraut 2006-11-17 16:46:27 +00:00
  • e1693e514c Rename replication section "High Availability and Load Balancing". Bruce Momjian 2006-11-17 16:38:44 +00:00
  • cc9698254c Data Partitioning documentation section reduced and moved to the end. Bruce Momjian 2006-11-17 13:29:53 +00:00
  • 42cfdfb453 Fix a typo. Neil Conway 2006-11-17 09:00:03 +00:00
  • 4b8049b815 Fixed small typo, missing 'l' in 'Cluserting' Michael Meskes 2006-11-17 08:46:53 +00:00
  • be4dbd9b26 Remove a bunch of antique information from the appendix in the docs that discusses CVS. Remove the recommendation to use cvs 1.10. Remove discussion of alleged CVSup binaries on postgresql.org, because they have not existed for several years. Remove discussion of how to build cvsup from source because the existing text is outdated, and more accurate information is available from the CVSup homepage. Neil Conway 2006-11-17 05:29:46 +00:00
  • 58a7efa03b Use more standard terms for replication, ideas from Markus Schiltknecht. Bruce Momjian 2006-11-17 04:52:46 +00:00
  • 8a6193333c Mention two-phase commit for having all transactions commit on all servers. Bruce Momjian 2006-11-16 21:45:25 +00:00
  • a1e5b5c832 Reconfigure failover/replication doc items to be varlist entries, rather than new sections, so they appear all on the same web page. Bruce Momjian 2006-11-16 21:43:33 +00:00
  • c7a6046a59 Clarify replication items, and define some terms. Bruce Momjian 2006-11-16 18:25:58 +00:00
  • e05a3c30b0 Message fix Peter Eisentraut 2006-11-16 14:41:49 +00:00