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

Commit Graph

  • 2c39737843 Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 under Windows. Per Magnus Hagander, this is not recommended. Neil Conway 2007-02-02 16:10:13 +00:00
  • 3714d82f76 Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 under Windows. Per Magnus Hagander, this is not recommended. Neil Conway 2007-02-02 16:10:10 +00:00
  • ee84009cb0 Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 under Windows. Per Magnus Hagander, this is not recommended. Neil Conway 2007-02-02 16:10:08 +00:00
  • 685523c420 Applied Magnus Hagander's patch to take away some compiler warnings. Michael Meskes 2007-02-02 09:31:10 +00:00
  • fc8115d42f Cleaned up va_list handling. Hopefully this now works on all archs. Michael Meskes 2007-02-02 08:58:23 +00:00
  • 98df90013f Add: Bruce Momjian 2007-02-02 05:42:56 +00:00
  • af8a424324 Stamp release 7.3.18. REL7_3_18 Tom Lane 2007-02-02 00:16:01 +00:00
  • de59c01f26 Stamp release 7.4.16. REL7_4_16 Tom Lane 2007-02-02 00:15:35 +00:00
  • d724689b73 Stamp release 8.0.11. REL8_0_11 Tom Lane 2007-02-02 00:15:09 +00:00
  • 924c1d4ceb Stamp release 8.1.7. REL8_1_7 Tom Lane 2007-02-02 00:14:48 +00:00
  • d06a16c589 Stamp release 8.2.2. REL8_2_2 Tom Lane 2007-02-02 00:14:22 +00:00
  • c07313161f Update release notes for security-related releases in all active branches. Tom Lane 2007-02-02 00:11:14 +00:00
  • abeae11765 Update release notes for security-related releases in all active branches. Tom Lane 2007-02-02 00:11:02 +00:00
  • 384f05d55a Update release notes for security-related releases in all active branches. Tom Lane 2007-02-02 00:10:51 +00:00
  • 43072a7ec1 Update release notes for security-related releases in all active branches. Tom Lane 2007-02-02 00:10:42 +00:00
  • 40cf433eb6 Update release notes for security-related releases in all active branches. Tom Lane 2007-02-02 00:10:33 +00:00
  • bd01a4e3b7 Update release notes for security-related releases in all active branches. Tom Lane 2007-02-02 00:10:23 +00:00
  • 7fbfa4e96a Repair failure to check that a table is still compatible with a previously made query plan. Use of ALTER COLUMN TYPE creates a hazard for cached query plans: they could contain Vars that claim a column has a different type than it now has. Fix this by checking during plan startup that Vars at relation scan level match the current relation tuple descriptor. Since at that point we already have at least AccessShareLock, we can be sure the column type will not change underneath us later in the query. However, since a backend's locks do not conflict against itself, there is still a hole for an attacker to exploit: he could try to execute ALTER COLUMN TYPE while a query is in progress in the current backend. Seal that hole by rejecting ALTER TABLE whenever the target relation is already open in the current backend. Tom Lane 2007-02-02 00:08:01 +00:00
  • 1f1f5efa82 Repair failure to check that a table is still compatible with a previously made query plan. Use of ALTER COLUMN TYPE creates a hazard for cached query plans: they could contain Vars that claim a column has a different type than it now has. Fix this by checking during plan startup that Vars at relation scan level match the current relation tuple descriptor. Since at that point we already have at least AccessShareLock, we can be sure the column type will not change underneath us later in the query. However, since a backend's locks do not conflict against itself, there is still a hole for an attacker to exploit: he could try to execute ALTER COLUMN TYPE while a query is in progress in the current backend. Seal that hole by rejecting ALTER TABLE whenever the target relation is already open in the current backend. Tom Lane 2007-02-02 00:07:44 +00:00
  • 23326cd18b Repair failure to check that a table is still compatible with a previously made query plan. Use of ALTER COLUMN TYPE creates a hazard for cached query plans: they could contain Vars that claim a column has a different type than it now has. Fix this by checking during plan startup that Vars at relation scan level match the current relation tuple descriptor. Since at that point we already have at least AccessShareLock, we can be sure the column type will not change underneath us later in the query. However, since a backend's locks do not conflict against itself, there is still a hole for an attacker to exploit: he could try to execute ALTER COLUMN TYPE while a query is in progress in the current backend. Seal that hole by rejecting ALTER TABLE whenever the target relation is already open in the current backend. Tom Lane 2007-02-02 00:07:28 +00:00
  • 5413eef8dc Repair failure to check that a table is still compatible with a previously made query plan. Use of ALTER COLUMN TYPE creates a hazard for cached query plans: they could contain Vars that claim a column has a different type than it now has. Fix this by checking during plan startup that Vars at relation scan level match the current relation tuple descriptor. Since at that point we already have at least AccessShareLock, we can be sure the column type will not change underneath us later in the query. However, since a backend's locks do not conflict against itself, there is still a hole for an attacker to exploit: he could try to execute ALTER COLUMN TYPE while a query is in progress in the current backend. Seal that hole by rejecting ALTER TABLE whenever the target relation is already open in the current backend. Tom Lane 2007-02-02 00:07:03 +00:00
  • 6be54294cb Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. Tom Lane 2007-02-02 00:04:16 +00:00
  • b4ddb79af5 Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. Tom Lane 2007-02-02 00:04:02 +00:00
  • f674971418 Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. Tom Lane 2007-02-02 00:03:44 +00:00
  • 088ef257fe Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. Tom Lane 2007-02-02 00:03:30 +00:00
  • 78e039cc2c Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. Tom Lane 2007-02-02 00:03:17 +00:00
  • f8eb75b673 Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. Tom Lane 2007-02-02 00:02:55 +00:00
  • dc4c26c37e Fix broken markup. Tom Lane 2007-02-01 22:06:14 +00:00
  • f7e5ecb026 Add "May/Can/Might" section to error message style guidlines, and "can't" -> "cannot" section. Bruce Momjian 2007-02-01 21:28:34 +00:00
  • 2576dd4dee Fix two more regression tests whose expected outputs were not updated for the recent may/might cleanup. Neil Conway 2007-02-01 21:05:29 +00:00
  • 14a866b18d Mention file system replication as a high availability solution in the shared hardware section, and mention DRBD as a popular solution. Bruce Momjian 2007-02-01 21:03:00 +00:00
  • 52096ae119 Mention file system replication as a high availability solution in the shared hardware section, and mention DRBD as a popular solution. Bruce Momjian 2007-02-01 21:02:48 +00:00
  • a9d5fb5a02 Typo fix. Tom Lane 2007-02-01 20:28:08 +00:00
  • d596efac56 Update some of the "expected" regression test results for Bruce's recent may/might cleanup, in the hopes that this will unbreak the buildfarm. Per report from Stefan Kaltenbrunner. Neil Conway 2007-02-01 20:11:18 +00:00
  • b7c9821146 Fix plpgsql so that when a local variable has no initial-value expression, an error will be thrown correctly if the variable is of a NOT NULL domain. Report and almost-correct fix from Sergiy Vyshnevetskiy (bug #2948). Tom Lane 2007-02-01 19:23:00 +00:00
  • 6994d0b891 Fix plpgsql so that when a local variable has no initial-value expression, an error will be thrown correctly if the variable is of a NOT NULL domain. Report and almost-correct fix from Sergiy Vyshnevetskiy (bug #2948). Tom Lane 2007-02-01 19:22:07 +00:00
  • 3c7d9add71 Backpatch last night's fix for broken markup to the 8.2 branch. Neil Conway 2007-02-01 19:18:14 +00:00
  • db047e571d Add URL for: Bruce Momjian 2007-02-01 19:13:56 +00:00
  • 8b4ff8b6a1 Wording cleanup for error messages. Also change can't -> cannot. Bruce Momjian 2007-02-01 19:10:30 +00:00
  • baaec74c5a Fix broken markup. Neil Conway 2007-02-01 07:00:32 +00:00
  • e3b12f76af Add 8.2.0 "Incomatibilities" documentation that pg_dump's -n and -t behavior has changed. Bruce Momjian 2007-02-01 05:12:46 +00:00
  • f1b68860bc Add 8.2.0 "Incomatibilities" documentation that pg_dump's -n and -t behavior has changed. Bruce Momjian 2007-02-01 05:12:24 +00:00
  • da45866c42 Backpatch FAQs to stable branch. Bruce Momjian 2007-02-01 04:56:41 +00:00
  • 969320c8b8 Chinese FAQ update Bruce Momjian 2007-02-01 04:55:53 +00:00
  • a867c5aa2f Update URL for function permission checks Bruce Momjian 2007-02-01 04:51:31 +00:00
  • 2ccb40b532 Add: Bruce Momjian 2007-02-01 04:50:58 +00:00
  • fa3f06dc6b Add: Bruce Momjian 2007-02-01 04:49:43 +00:00
  • bd2c171414 This patch adds documentation for the long-version parameters --username and --password for pg_dump, pg_dumpall and pg_restore, per complaint by Michael Schmidt. Patch from Magnus Hagander. Neil Conway 2007-02-01 04:39:33 +00:00
  • e665137250 Add: > > * Fix problem when multiple subtransactions of the same outer transaction > hold different types of locks, and one subtransaction aborts > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php Bruce Momjian 2007-02-01 04:35:52 +00:00
  • dbcaee49b5 Fix a few typos in comments in GiN. Neil Conway 2007-02-01 04:16:08 +00:00
  • b3687889c4 Update CREATE SEQUENCE documentation to show the same sequence being created and increments. The old docs created the sequence, then showed a nextval() of 114. Bruce Momjian 2007-02-01 00:34:03 +00:00
  • 40bf8717cf Add URL for: Bruce Momjian 2007-02-01 00:32:45 +00:00
  • 09a9f10e7f Consistenly use colons before '<programlisting>' blocks, where appropriate. Bruce Momjian 2007-02-01 00:28:19 +00:00
  • e81c138e18 Update reference documentation on may/can/might: Bruce Momjian 2007-01-31 23:26:05 +00:00
  • bc799fab2b Update comment. Bruce Momjian 2007-01-31 22:17:03 +00:00
  • 482e6936fa Revert error message change for may/can/might --- needs discussion. Bruce Momjian 2007-01-31 21:03:37 +00:00
  • a134ee3379 Update documentation on may/can/might: Bruce Momjian 2007-01-31 20:56:20 +00:00
  • 67a1ae9f05 Add missing Makefile dependencies for the "bigtest" and "bigcheck" targets, and refactor the tablespace setup code into a separate Makefile target. Neil Conway 2007-01-31 19:38:50 +00:00
  • 05ce7d6a41 Rewrite uuid input and output routines to avoid dependency on the nonportable "hh" sprintf(3) length modifier. Instead, do the parsing and output by hand. The code to do this isn't ideal, but this is an interim measure anyway: the uuid type should probably use the in-memory struct layout specified by RFC 4122. For now, this patch should hopefully rectify the buildfarm failures for the uuid test. Neil Conway 2007-01-31 19:33:54 +00:00
  • 068bf6534f Fix initdb to not generate misleading error messages when postgres.bki or other share-directory files are inaccessible for some reason other than not existing. Inspired by trouble report from Simon Kinsella. Tom Lane 2007-01-31 18:52:49 +00:00
  • 61f621b506 Revert gincostestimate changes. Teodor Sigaev 2007-01-31 16:54:51 +00:00
  • b62f85691e Update FreeBSD DocBook installation notices Teodor Sigaev 2007-01-31 15:23:28 +00:00
  • d4c6da1527 Allow GIN's extractQuery method to signal that nothing can satisfy the query. In this case extractQuery should returns -1 as nentries. This changes prototype of extractQuery method to use int32* instead of uint32* for nentries argument. Based on that gincostestimate may see two corner cases: nothing will be found or seqscan should be used. Teodor Sigaev 2007-01-31 15:09:45 +00:00
  • 1762c4316e Translation updates Peter Eisentraut 2007-01-31 08:33:34 +00:00
  • 139e4a2635 Translation updates Peter Eisentraut 2007-01-31 08:27:01 +00:00
  • a258f9c6de Translation updates Peter Eisentraut 2007-01-31 08:20:42 +00:00
  • 65ada7c810 Translation updates Peter Eisentraut 2007-01-31 08:12:56 +00:00
  • cf9ca3d2a3 Translation updates Peter Eisentraut 2007-01-31 08:05:43 +00:00
  • 147a3ce149 Add URL: Bruce Momjian 2007-01-31 04:23:47 +00:00
  • 8c14912cc1 Document need for periodic REINDEX in VACUUM FULL cases. Bruce Momjian 2007-01-31 04:13:28 +00:00
  • 0867493510 Document need for periodic REINDEX in VACUUM FULL cases. Bruce Momjian 2007-01-31 04:13:22 +00:00
  • 1a62813464 Add missing colon. Bruce Momjian 2007-01-31 04:12:01 +00:00
  • 99507b9a92 Add: Bruce Momjian 2007-01-31 03:17:49 +00:00
  • 62b2786b82 Update for VACUUM FULL: Bruce Momjian 2007-01-31 03:07:36 +00:00
  • aca00a8b98 Add: > o ARRAY[[1,2],[3,4]])[1] should return the same values as > ARRAY[[1,2],[3,4]])[1:1]; > Bruce Momjian 2007-01-30 22:55:12 +00:00
  • 91a753f68b Add FAQ item about timezones and daylight savings time. Bruce Momjian 2007-01-30 22:37:15 +00:00
  • e2d6898827 Update documentation for backslashes to mention escape string syntax more, and standard_conforming_strings less, because in the future non-E strings will not treat backslashes specially. Bruce Momjian 2007-01-30 22:29:40 +00:00
  • 4ed9f1d9b7 Update documentation for backslashes to mention escape string syntax more, and standard_conforming_strings less, because in the future non-E strings will not treat backslashes specially. Bruce Momjian 2007-01-30 22:29:23 +00:00
  • 6c74f05cf2 Repair oversights in the mechanism used to store compiled plpgsql functions. The original coding failed (tried to access deallocated memory) if there were two active call sites (fn_extra pointers) for the same function and the function definition was updated. Also, if an update of a recursive function was detected upon nested entry to the function, the existing compiled version was summarily deallocated, resulting in crash upon return to the outer instance. Problem observed while studying a bug report from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 22:05:25 +00:00
  • 08c17d6e56 Repair oversights in the mechanism used to store compiled plpgsql functions. The original coding failed (tried to access deallocated memory) if there were two active call sites (fn_extra pointers) for the same function and the function definition was updated. Also, if an update of a recursive function was detected upon nested entry to the function, the existing compiled version was summarily deallocated, resulting in crash upon return to the outer instance. Problem observed while studying a bug report from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 22:05:20 +00:00
  • 35b039a26c Repair oversights in the mechanism used to store compiled plpgsql functions. The original coding failed (tried to access deallocated memory) if there were two active call sites (fn_extra pointers) for the same function and the function definition was updated. Also, if an update of a recursive function was detected upon nested entry to the function, the existing compiled version was summarily deallocated, resulting in crash upon return to the outer instance. Problem observed while studying a bug report from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 22:05:13 +00:00
  • 052e884e8b Add SPI_push/SPI_pop calls so that datatype input and output functions called by plpgsql can themselves use SPI --- possibly indirectly, as in the case of domain_in() invoking plpgsql functions in a domain check constraint. Per bug #2945 from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 18:02:40 +00:00
  • 458e9169d6 Add SPI_push/SPI_pop calls so that datatype input and output functions called by plpgsql can themselves use SPI --- possibly indirectly, as in the case of domain_in() invoking plpgsql functions in a domain check constraint. Per bug #2945 from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 18:02:34 +00:00
  • 971230dfbb Add SPI_push/SPI_pop calls so that datatype input and output functions called by plpgsql can themselves use SPI --- possibly indirectly, as in the case of domain_in() invoking plpgsql functions in a domain check constraint. Per bug #2945 from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 18:02:28 +00:00
  • 33d78c9e48 Add SPI_push/SPI_pop calls so that datatype input and output functions called by plpgsql can themselves use SPI --- possibly indirectly, as in the case of domain_in() invoking plpgsql functions in a domain check constraint. Per bug #2945 from Sergiy Vyshnevetskiy. Tom Lane 2007-01-30 18:02:22 +00:00
  • ae875d318e Update documentation for pg_get_serial_sequence() function. Bruce Momjian 2007-01-30 02:39:27 +00:00
  • c22f642f2f Clarify paramater handling for pg_get_serial_sequence(). Bruce Momjian 2007-01-30 02:32:05 +00:00
  • a635c08fa1 Add support for cross-type hashing in hash index searches and hash joins. Hashing for aggregation purposes still needs work, so it's not time to mark any cross-type operators as hashable for general use, but these cases work if the operators are so marked by hand in the system catalogs. Tom Lane 2007-01-30 01:33:36 +00:00
  • e8cd6f14a2 Add comment noting that hashm_procid in a hash index's metapage isn't actually used for anything. Tom Lane 2007-01-29 23:22:59 +00:00
  • c120dd263b Update wording for minor release upgrades, per Alvaro. Bruce Momjian 2007-01-29 21:49:17 +00:00
  • 631d7018df Done: Bruce Momjian 2007-01-29 21:19:30 +00:00
  • a6017cff0b Use sizeof() for snprintf() buffer length. Bruce Momjian 2007-01-29 20:22:35 +00:00
  • 5b4fa95984 Update process termination message to display signal number and name from exec.c and postmaster.c. Bruce Momjian 2007-01-29 20:17:40 +00:00
  • 48ba3f5711 Update documentation on XML functions Peter Eisentraut 2007-01-29 13:24:30 +00:00
  • b39e91501c Improve hash join to discard input tuples immediately if they can't match because they contain a null join key (and the join operator is known strict). Improves performance significantly when the inner relation contains a lot of nulls, as per bug #2930. Tom Lane 2007-01-28 23:21:26 +00:00
  • 28c480e9ae Remove unnecessary checkpoint from PL regression tests. This was once handy to prevent core dump files from disappearing, but it's useless now because (a) we don't drop core in individual DB subdirectories anymore, and (b) CREATE DATABASE forces an internal checkpoint anyway. Tom Lane 2007-01-28 21:17:32 +00:00
  • 74a1a2b8b1 Rename the uuid_t type to pg_uuid_t, to avoid a conflict with any definitions of uuid_t that may be provided by the system headers. This should hopefully fix the Win32 build problems reported by Magnus. Neil Conway 2007-01-28 20:25:38 +00:00
  • cd47d0f781 Fix plpython MSVC build in non-debug mode. Andrew Dunstan 2007-01-28 19:36:46 +00:00
  • 529a24a22b Remove some unnecessary conversion work in build_regtype_array(). Tom Lane 2007-01-28 19:05:35 +00:00
  • 01d9754bd9 Repair oversight in creation of "append relations": we should set up rel->tuples as well as rel->rows, since some estimation functions expect both to be valid in every baserel. Per report from Dave Dutcher. Tom Lane 2007-01-28 18:50:48 +00:00