Commit Graph

  • 28997903a1 Handle missing M_PI the same way we've been doing in the core code, instead of inserting an MSVC dependency. Tom Lane 2006-10-19 20:08:03 +00:00
  • f6e00ae128 Further MSVC portability fixes from Magnus. Tom Lane 2006-10-19 20:03:08 +00:00
  • 6bc1f9b334 Remove qsort TODO.detail. All items completed. Bruce Momjian 2006-10-19 19:59:06 +00:00
  • a60af96a00 Done: Bruce Momjian 2006-10-19 19:58:45 +00:00
  • 2315df21f8 Fix a couple of places that were assuming debug_query_string couldn't be NULL ... seems an unsafe assumption. Tom Lane 2006-10-19 19:53:03 +00:00
  • 681892208f Make sure that debug_query_string contains the original query text, if available (which it usually should be), during processing of Bind and Execute protocol messages. This improves usefulness of log_min_error_statement logging for extended query protocol. Tom Lane 2006-10-19 19:52:22 +00:00
  • def651f48f Clean up local redeclarations of variables with DLLIMPORT, per report from Magnus that MSVC complains about this. Tom Lane 2006-10-19 18:32:48 +00:00
  • fd38d726a9 Fix typo. Neil Conway 2006-10-19 17:48:04 +00:00
  • 72ec567a9a Simplify contrib Makefiles by removing unnecessary SRCS macro, per Magnus. Tom Lane 2006-10-19 17:40:03 +00:00
  • 8df0bcc696 Work around reported problem that AIX's getaddrinfo() doesn't seem to zero sin_port in the returned IP address struct when servname is NULL. This has been observed to cause failure to bind the stats collection socket, and could perhaps cause other issues too. Per reports from Brad Nicholson and Chris Browne. Tom Lane 2006-10-19 17:26:51 +00:00
  • 375cb7cfb0 Work around reported problem that AIX's getaddrinfo() doesn't seem to zero sin_port in the returned IP address struct when servname is NULL. This has been observed to cause failure to bind the stats collection socket, and could perhaps cause other issues too. Per reports from Brad Nicholson and Chris Browne. Tom Lane 2006-10-19 17:26:43 +00:00
  • 62fc3b9929 Work around reported problem that AIX's getaddrinfo() doesn't seem to zero sin_port in the returned IP address struct when servname is NULL. This has been observed to cause failure to bind the stats collection socket, and could perhaps cause other issues too. Per reports from Brad Nicholson and Chris Browne. Tom Lane 2006-10-19 17:26:37 +00:00
  • dbb397f30f Work around reported problem that AIX's getaddrinfo() doesn't seem to zero sin_port in the returned IP address struct when servname is NULL. This has been observed to cause failure to bind the stats collection socket, and could perhaps cause other issues too. Per reports from Brad Nicholson and Chris Browne. Tom Lane 2006-10-19 17:26:32 +00:00
  • 1e758d5263 Add some code to CREATE DATABASE to check for pre-existing subdirectories that conflict with the OID that we want to use for the new database. This avoids the risk of trying to remove files that maybe we shouldn't remove. Per gripe from Jon Lapham and subsequent discussion of 27-Sep. Tom Lane 2006-10-18 22:44:12 +00:00
  • 877f08da14 Fix up timetz input so that a date is required only when the specified timezone actually has a daylight-savings rule. This avoids breaking cases that used to work because they went through the DecodePosixTimezone code path. Per contrib regression failures (mea culpa for not running those yesterday...). Also document the already-applied change to allow GMT offsets up to 14 hours. Tom Lane 2006-10-18 16:43:14 +00:00
  • 723f716be0 Fix array operator refererence in release notes, per David Wheeler. Bruce Momjian 2006-10-18 03:53:50 +00:00
  • 022fd99668 Fix up some problems in handling of zic-style time zone names in datetime input routines. Remove the former "DecodePosixTimezone" function in favor of letting the zic code handle POSIX-style zone specs (see tzparse()). In particular this means that "PST+3" now means the same as "-03", whereas it used to mean "-11" --- the zone abbreviation is effectively just a noise word in this syntax. Make sure that all named and POSIX-style zone names will be parsed as a single token. Fix long-standing bogosities in printing and input of fractional-hour timezone offsets (since the tzparse() code will accept these, we'd better make 'em work). Also correct an error in the original coding of the zic-zone-name patch: in "timestamp without time zone" input, zone names are supposed to be allowed but ignored, but the coding was such that the zone changed the interpretation anyway. Tom Lane 2006-10-17 21:03:21 +00:00
  • d58f09e6b3 Mark 8.2 release as 2006-??, not 2005-??, per observation by David Wheeler. Bruce Momjian 2006-10-17 20:17:08 +00:00
  • 47fecaf504 Attached files fix the link problem in FAQ_DEV.html, remove some parts related to website development and change the link to the FAQ_DEV.html. Bruce Momjian 2006-10-17 12:54:45 +00:00
  • 10d9bbaf01 Fixes for CREATE CONSTRAINT manual page. Bruce Momjian 2006-10-17 12:53:03 +00:00
  • 14914e0d33 Fix unexpected side-effect of changes for case insensitivity of timezone names. Tom Lane 2006-10-17 02:21:46 +00:00
  • 3e584e071b Remove use of whrandom module, which was removed in Python 2.5. Peter Eisentraut 2006-10-16 21:13:57 +00:00
  • 0b35b01e7a Arrange for timezone names to be recognized case-insensitively; for example SET TIME ZONE 'america/new_york' works now. This seems a good idea on general user-friendliness grounds, and is part of the solution to the timestamp-input parsing problems I noted recently. Tom Lane 2006-10-16 19:58:27 +00:00
  • a2ebf81913 CREATE CONSTRAINT manual page wording improvements. Bruce Momjian 2006-10-16 19:33:12 +00:00
  • 52831f7911 Update to CREATE CONSTRAINT manual page. Bruce Momjian 2006-10-16 19:30:09 +00:00
  • c2e7da1f62 I updated RPM related parts in FAQ_DEV against HEAD to be more current. Bruce Momjian 2006-10-16 19:03:43 +00:00
  • 389fad1e6b Remove use of '<' and '>' in SGML, use '&' escapes. Bruce Momjian 2006-10-16 17:28:03 +00:00
  • 6ab23dabf5 Punt when trying to build with threaded Python on FreeBSD. Peter Eisentraut 2006-10-16 17:24:54 +00:00
  • e0dece127d Redesign the patch for allocation of shmem space and LWLocks for add-on modules; the first try was not usable in EXEC_BACKEND builds (e.g., Windows). Instead, just provide some entry points to increase the allocation requests during postmaster start, and provide a dedicated LWLock that can be used to synchronize allocation operations performed by backends. Per discussion with Marc Munro. Tom Lane 2006-10-15 22:04:08 +00:00
  • a3dff39c53 Adjust plperl to ensure that all strings and hash keys passed to Perl are marked as UTF8 when the database encoding is UTF8. This should avoid inconsistencies like that exhibited in bug #2683 from Vitali Stupin. Tom Lane 2006-10-15 18:56:39 +00:00
  • 87eed2e3e1 Update Japanese FAQ. Bruce Momjian 2006-10-15 03:10:20 +00:00
  • fdbe9facdc FAQ updates --- This is a small cosmetic patch that adds pt_BR IRC channel to the lists of IRC channels, fixes a typo in the OID's question, and corrects the PGCluster's project name. Bruce Momjian 2006-10-14 23:08:48 +00:00
  • 1314983fd3 Code review for --no-data-for-failed-tables patch. Instead of trashing one of the program's core data structures, make use of the existing ability to selectively exclude TOC items by ID. Slightly more code but much less likely to create future maintenance problems. Tom Lane 2006-10-14 23:07:22 +00:00
  • f58eac82ee Code and docs review for ALTER TABLE INHERIT/NO INHERIT patch. Tom Lane 2006-10-13 21:43:19 +00:00
  • e1fdd2263f Make unknown-option-warning code more portable. echo -n is not portable, and neither is "|" or "\|" in basic regular expressions. Peter Eisentraut 2006-10-13 20:23:07 +00:00
  • 09b98773ab Update Japanese FAQ. Bruce Momjian 2006-10-13 17:30:13 +00:00
  • d63ddfb872 Update Japanese FAQ. Bruce Momjian 2006-10-13 17:29:43 +00:00
  • 91ddf5b548 Fix typo in version number. Tom Lane 2006-10-13 15:25:09 +00:00
  • 7de6cf2743 Fix typo in version number. Tom Lane 2006-10-13 15:24:56 +00:00
  • 5777dca4f8 Fix test_fsync compile on MinGW(win32) Bruce Momjian 2006-10-13 14:19:29 +00:00
  • 10a6e431d3 Fix infinite sleep and failes of send in Win32. Teodor Sigaev 2006-10-13 14:00:41 +00:00
  • 9f1b531420 Fix infinite sleep and failes of send in Win32. Teodor Sigaev 2006-10-13 14:00:17 +00:00
  • 47df6e7e2d Fix infinite sleep and failes of send in Win32. Teodor Sigaev 2006-10-13 13:59:47 +00:00
  • efa0e8639f Remove: Bruce Momjian 2006-10-12 22:33:04 +00:00
  • ab1cec93c5 Add url's for hints: Bruce Momjian 2006-10-12 21:40:15 +00:00
  • 5ee7c794c7 Add: Bruce Momjian 2006-10-12 21:29:24 +00:00
  • 53d7eece13 Stamp 7.3.16. REL7_3_16 Tom Lane 2006-10-12 19:42:21 +00:00
  • 62f9cbf424 Stamp 7.4.14. REL7_4_14 Tom Lane 2006-10-12 19:42:03 +00:00
  • 9a0d9968b2 Stamp 8.0.9. REL8_0_9 Tom Lane 2006-10-12 19:41:43 +00:00
  • 87d57b6c93 Stamp 8.1.5. REL8_1_5 Tom Lane 2006-10-12 19:41:27 +00:00
  • bfc6e9c970 Make some incremental improvements and fixes to the documentation on Continuous Archiving. Plenty of editorial work remains... Neil Conway 2006-10-12 19:38:08 +00:00
  • 424157a803 Sync 8.1 pg_config.h.in with expected autoheader output (looks like someone did this manually last time ...) Tom Lane 2006-10-12 19:29:30 +00:00
  • db9ebafca1 Update release notes for SQL functions vs triggers fix. Tom Lane 2006-10-12 19:25:32 +00:00
  • 9d457ea802 Update release notes for SQL functions vs triggers fix. Tom Lane 2006-10-12 19:25:22 +00:00
  • 0c9983889a Update release notes for SQL functions vs triggers fix. Tom Lane 2006-10-12 19:25:12 +00:00
  • 7055867a01 In the installation docs, add some links to the documentation on LDAP to the discussion of the "--with-ldap" configure option. Patch from Albe Laurenz. Neil Conway 2006-10-12 18:49:32 +00:00
  • 9a0271bd31 Fix mishandling of after-trigger state when a SQL function returns multiple rows --- if the surrounding query queued any trigger events between the rows, the events would be fired at the wrong time, leading to bizarre behavior. Per report from Merlin Moncure. Tom Lane 2006-10-12 17:02:34 +00:00
  • fb27f43123 Fix mishandling of after-trigger state when a SQL function returns multiple rows --- if the surrounding query queued any trigger events between the rows, the events would be fired at the wrong time, leading to bizarre behavior. Per report from Merlin Moncure. Tom Lane 2006-10-12 17:02:28 +00:00
  • d2e17e1ddc Fix mishandling of after-trigger state when a SQL function returns multiple rows --- if the surrounding query queued any trigger events between the rows, the events would be fired at the wrong time, leading to bizarre behavior. Per report from Merlin Moncure. Tom Lane 2006-10-12 17:02:24 +00:00
  • b38900c767 Use Min() instead of min() in qsort, for consistency and to avoid redefined-macro warnings on some platforms. Per gripe from Hiroshi Saito. Tom Lane 2006-10-12 15:04:55 +00:00
  • a50606de91 Remove somebody's ill-considered free() call, per report from Chander Ganesan. No, I do not care whether Coverity considers this a memory leak. It's entirely not worth the code space to do it correctly. Tom Lane 2006-10-12 05:14:49 +00:00
  • 638cc9abf8 Update pg_hba.conf comment about documentation section. Bruce Momjian 2006-10-11 23:01:46 +00:00
  • 9dd224e3c6 A bit of copy-editing on back-branch release notes. Tom Lane 2006-10-11 20:56:31 +00:00
  • 1d5ad22c32 A bit of copy-editing on back-branch release notes. Tom Lane 2006-10-11 20:56:21 +00:00
  • b6a71905d3 A bit of copy-editing on back-branch release notes. Tom Lane 2006-10-11 20:56:10 +00:00
  • 23c64e18ec A bit of copy-editing on back-branch release notes. Tom Lane 2006-10-11 20:56:01 +00:00
  • 953c85646e A bit of copy-editing on back-branch release notes. Tom Lane 2006-10-11 20:55:52 +00:00
  • 47cec0327e Repair incorrect check for coercion of unknown literal to ANYARRAY, a bug I introduced in 7.4.1 :-(. It's correct to allow unknown to be coerced to ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly isn't an array datatype. This can cause a backend crash but AFAICT is not exploitable as a security hole. Per report from Michael Fuhr. Tom Lane 2006-10-11 20:21:28 +00:00
  • dc167085f3 Repair incorrect check for coercion of unknown literal to ANYARRAY, a bug I introduced in 7.4.1 :-(. It's correct to allow unknown to be coerced to ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly isn't an array datatype. This can cause a backend crash but AFAICT is not exploitable as a security hole. Per report from Michael Fuhr. Tom Lane 2006-10-11 20:21:19 +00:00
  • c2caa7b736 Repair incorrect check for coercion of unknown literal to ANYARRAY, a bug I introduced in 7.4.1 :-(. It's correct to allow unknown to be coerced to ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly isn't an array datatype. This can cause a backend crash but AFAICT is not exploitable as a security hole. Per report from Michael Fuhr. Tom Lane 2006-10-11 20:21:11 +00:00
  • 772c5ba31f Repair incorrect check for coercion of unknown literal to ANYARRAY, a bug I introduced in 7.4.1 :-(. It's correct to allow unknown to be coerced to ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly isn't an array datatype. This can cause a backend crash but AFAICT is not exploitable as a security hole. Per report from Michael Fuhr. Tom Lane 2006-10-11 20:21:04 +00:00
  • 1c2d02c499 CREATE TABLE ... LIKE ... should mark the columns it creates with attislocal = true, since they are not really inherited but merely copied from the original table. I'm not sure if there are any cases where it makes a real difference given the existing uses of the flag, but wrong is wrong. This was fixed in passing in HEAD by the LIKE INCLUDING CONSTRAINTS patch, but never back-patched. Tom Lane 2006-10-11 20:03:26 +00:00
  • 8608aa9534 CREATE TABLE ... LIKE ... should mark the columns it creates with attislocal = true, since they are not really inherited but merely copied from the original table. I'm not sure if there are any cases where it makes a real difference given the existing uses of the flag, but wrong is wrong. This was fixed in passing in HEAD by the LIKE INCLUDING CONSTRAINTS patch, but never back-patched. Tom Lane 2006-10-11 20:03:18 +00:00
  • 97fc0f6e83 CREATE TABLE ... LIKE ... should mark the columns it creates with attislocal = true, since they are not really inherited but merely copied from the original table. I'm not sure if there are any cases where it makes a real difference given the existing uses of the flag, but wrong is wrong. This was fixed in passing in HEAD by the LIKE INCLUDING CONSTRAINTS patch, but never back-patched. Tom Lane 2006-10-11 20:03:11 +00:00
  • 8f2f180ff1 Code review for LIKE INCLUDING CONSTRAINTS patch --- improve comments, don't cheat on the raw-vs-cooked status of a constraint. Tom Lane 2006-10-11 16:42:59 +00:00
  • 3f16647960 Rename function 'isexists' and 'isdefined' to 'exist' and 'defined' accordingly. Old names are saved not mentioned in docs - for compatibility with old applications. Per discussion http://archives.postgresql.org/pgsql-hackers/2006-10/msg00571.php Teodor Sigaev 2006-10-11 16:42:51 +00:00
  • 4e46f4799e Cleanup pass Peter Eisentraut 2006-10-10 22:19:08 +00:00
  • ed95aea27d MSVC/BCC Win32 compiler fixes. Bruce Momjian 2006-10-10 21:31:44 +00:00
  • 34cd09fdd0 Restore HPUX FAQ entry that talked about working around regression script problems, because in 8.1.X, the regression test is still a script. Patch to 8.1.X only. Bruce Momjian 2006-10-10 20:11:44 +00:00
  • 7275173636 Fix psql \d commands to behave properly when a pattern using regex | is given. Formerly they'd emit '^foo|bar$' which is wrong because the anchors are parsed as part of the alternatives; must emit '^(foo|bar)$' to get expected behavior. Same as bug found previously in similar_escape(). Already fixed in HEAD, this is just back-porting the part of that patch that was a bug fix. Tom Lane 2006-10-10 16:15:42 +00:00
  • 7b165e3ba5 Fix psql \d commands to behave properly when a pattern using regex | is given. Formerly they'd emit '^foo|bar$' which is wrong because the anchors are parsed as part of the alternatives; must emit '^(foo|bar)$' to get expected behavior. Same as bug found previously in similar_escape(). Already fixed in HEAD, this is just back-porting the part of that patch that was a bug fix. Tom Lane 2006-10-10 16:15:37 +00:00
  • 13abcaba80 Fix psql \d commands to behave properly when a pattern using regex | is given. Formerly they'd emit '^foo|bar$' which is wrong because the anchors are parsed as part of the alternatives; must emit '^(foo|bar)$' to get expected behavior. Same as bug found previously in similar_escape(). Already fixed in HEAD, this is just back-porting the part of that patch that was a bug fix. Tom Lane 2006-10-10 16:15:28 +00:00
  • 9c2b6ec695 Fix psql \d commands to behave properly when a pattern using regex | is given. Formerly they'd emit '^foo|bar$' which is wrong because the anchors are parsed as part of the alternatives; must emit '^(foo|bar)$' to get expected behavior. Same as bug found previously in similar_escape(). Already fixed in HEAD, this is just back-porting the part of that patch that was a bug fix. Tom Lane 2006-10-10 16:15:22 +00:00
  • 04209052ba Typo fix. Bruce Momjian 2006-10-10 00:30:32 +00:00
  • 327d5c3571 Add release checklist item: Bruce Momjian 2006-10-10 00:30:18 +00:00
  • 61c91fd2d2 Backpatch FAQs to 8.1.X. Bruce Momjian 2006-10-10 00:29:15 +00:00
  • 16795b9899 Update FAQ for latest release 8.1.5. Bruce Momjian 2006-10-10 00:28:32 +00:00
  • f3fa771ccf Update libpq.rc for 7.3.16 and 7.4.14. Later releases use libpq.rc.in, which was already updated. Bruce Momjian 2006-10-10 00:19:58 +00:00
  • b25ddbb81e Update libpq.rc for 7.3.16 and 7.4.14. Later releases use libpq.rc.in, which was already updated. Bruce Momjian 2006-10-10 00:19:51 +00:00
  • 7cec8b4e4a Stamp releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:39:03 +00:00
  • bc0fa10440 Stamp releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:38:46 +00:00
  • 10d46101f9 Stamp releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:38:34 +00:00
  • 68b856f065 Stamp releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:38:14 +00:00
  • 24e9752863 Revise psql pattern-matching switches as per discussion. The rule is now to process all inclusion switches then all exclusion switches, so that the behavior is independent of switch ordering. Use of -T does not cause non-table objects to be suppressed. And the patterns are now interpreted the same way psql's \d commands do it, rather than as pure regex commands; this allows for example -t schema.tab to do what it should have been doing all along. Re-enable the --blobs switch to do something useful, ie, add back blobs into a dump they were otherwise suppressed from. Tom Lane 2006-10-09 23:36:59 +00:00
  • 77d2b1b625 Improve description of the pattern matching rules used by psql's \d commands (and soon by pg_dump). Tom Lane 2006-10-09 23:31:29 +00:00
  • 39ed8c4049 Move processNamePattern into dumputils.c in preparation for using it in pg_dump as well as psql. Since psql already uses dumputils.c, while there's not any code sharing in the other direction, this seems the easiest way. Also, fix misinterpretation of patterns using regex | by adding parentheses (same bug found previously in similar_escape()). This should be backpatched. Tom Lane 2006-10-09 23:30:33 +00:00
  • 5c13747ac9 Update release notes for releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:24:06 +00:00
  • d9dddd1100 Update release notes for releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:23:47 +00:00
  • b07bda6312 Update release notes for releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:23:29 +00:00
  • f18ace69dc Update release notes for releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5. Bruce Momjian 2006-10-09 23:23:11 +00:00