summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2007-02-06Docs updates for cross-type hashing.Tom Lane
2007-02-06Come to think of it, we should check that commutator pairs have the sameTom Lane
merges/hashes property settings.
2007-02-06Not only did we agree that this 'hint' doesn't belong here, but theTom Lane
markup's broken. So just remove it...
2007-02-06Add support for cross-type hashing in hashed subplans (hashed IN/NOT IN casesTom Lane
that aren't turned into true joins). Since this is the last missing bit of infrastructure, go ahead and fill out the hash integer_ops and float_ops opfamilies with cross-type operators. The operator family project is now DONE ... er, except for documentation ...
2007-02-05Trim down environment variable instructions for Win32, backpatch to 8.2.X.Bruce Momjian
2007-02-05Updated TODO item:Bruce Momjian
> o Add a \set variable to control whether \s displays line numbers > Another option is to add \# which lists line numbers, and > allows command execution. > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
2007-02-05Modify:Bruce Momjian
< o Add \# to list command history like \s, but with line numbers > o Add \# to list and execute command history
2007-02-05Pass modern COPY syntax to backend, since copy (query) does not accept old ↵Andrew Dunstan
syntax. Per complaint from Michael Fuhr.
2007-02-05Rename MaxTupleSize to MaxHeapTupleSize to clarify that it's not meant toTom Lane
describe the maximum size of index tuples (which is typically AM-dependent anyway); and consequently remove the bogus deduction for "special space" that was built into it. Adjust TOAST_TUPLE_THRESHOLD and TOAST_MAX_CHUNK_SIZE to avoid wasting two bytes per toast chunk, and to ensure that the calculation correctly tracks any future changes in page header size. The computation had been inaccurate in a way that didn't cause any harm except space wastage, but future changes could have broken it more drastically. Fix the calculation of BTMaxItemSize, which was formerly computed as 1 byte more than it could safely be. This didn't cause any harm in practice because it's only compared against maxalign'd lengths, but future changes in the size of page headers or btree special space could have exposed the problem. initdb forced because of change in TOAST_MAX_CHUNK_SIZE, which alters the storage of toast tables.
2007-02-04Don't MAXALIGN in the checks to decide whether a tuple is over TOAST'sTom Lane
threshold for tuple length. On 4-byte-MAXALIGN machines, the toast code creates tuples that have t_len exactly TOAST_TUPLE_THRESHOLD ... but this number is not itself maxaligned, so if heap_insert maxaligns t_len before comparing to TOAST_TUPLE_THRESHOLD, it'll uselessly recurse back to tuptoaster.c, wasting cycles. (It turns out that this does not happen on 8-byte-MAXALIGN machines, because for them the outer MAXALIGN in the TOAST_MAX_CHUNK_SIZE macro reduces TOAST_MAX_CHUNK_SIZE so that toast tuples will be less than TOAST_TUPLE_THRESHOLD in size. That MAXALIGN is really incorrect, but we can't remove it now, see below.) There isn't any particular value in maxaligning before comparing to the thresholds, so just don't do that, which saves a small number of cycles in itself. These numbers should be rejiggered to minimize wasted space on toast-relation pages, but we can't do that in the back branches because changing TOAST_MAX_CHUNK_SIZE would force an initdb (by changing the contents of toast tables). We can move the toast decision thresholds a bit, though, which is what this patch effectively does. Thanks to Pavan Deolasee for discovering the unintended recursion. Back-patch into 8.2, but not further, pending more testing. (HEAD is about to get a further patch modifying the thresholds, so it won't help much for testing this form of the patch.)
2007-02-04Add:Bruce Momjian
> > * Allow custom variable classes that can restrict who can set the values > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php >
2007-02-04Update wording.Bruce Momjian
2007-02-04Add documentation for Windows on how to set an environment variable.Bruce Momjian
Backpatch to 8.2.X.
2007-02-04Change vacuum lazy "compacting" warning message to:Bruce Momjian
errhint("Consider using VACUUM FULL on this relation or increasing the configuration parameter \"max_fsm_pages\".")));
2007-02-04Update URL for:Bruce Momjian
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning"
2007-02-04Add:Bruce Momjian
> > o Add \# to list command history like \s, but with line numbers > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php >
2007-02-03Add URLs for:Bruce Momjian
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" > http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
2007-02-03Document that a client-only install using:Bruce Momjian
gmake -C src/bin install does install a few server-only binaries.
2007-02-03Add:Bruce Momjian
> o Allow recovery.conf to allow the same syntax as > postgresql.conf, including quoting > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
2007-02-03Update SQL conformance information about XML features.Peter Eisentraut
2007-02-03Implement XMLSERIALIZE for real. Analogously, make the xml to text castPeter Eisentraut
observe the xmloption. Reorganize the representation of the XML option in the parse tree and the API to make it easier to manage and understand. Add regression tests for parsing back XML expressions.
2007-02-03Fix configure detection code when --with-ldap and --enable-thread-safetyBruce Momjian
are both used. Albe Laurenz
2007-02-03Add patches thread for:Bruce Momjian
* Reduce checkpoint performance degredation by forcing data to disk more evenly > http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php
2007-02-02Add URL for:Bruce Momjian
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php
2007-02-02Add:Bruce Momjian
> * Reduce checkpoint performance degredation by forcing data to disk > more evenly > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php
2007-02-02Add URL for:Bruce Momjian
o Fix RENAME to work on variables other than OLD/NEW > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
2007-02-02This patch changes the installscript for vcbuild to actually parse theNeil Conway
generated solution files for what to install, instead of blindly copying everything as it previously did. With the previous quick-n-dirty version, it would copy old DLLs if you reconfigured in a way that didn't include subprojects like a PL for example. Magnus Hagander.
2007-02-02Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 underNeil Conway
Windows. Per Magnus Hagander, this is not recommended.
2007-02-02Applied Magnus Hagander's patch to take away some compiler warnings.Michael Meskes
2007-02-02Cleaned up va_list handling. Hopefully this now works on all archs.Michael Meskes
2007-02-02Add:Bruce Momjian
> o Allow column display reordering by recording a display, > storage, and permanent id for every column? > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php >
2007-02-02Update release notes for security-related releases in all active branches.Tom Lane
Security: CVE-2007-0555, CVE-2007-0556
2007-02-02Repair failure to check that a table is still compatible with a previouslyTom Lane
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. This is a significant security hole: not only can one trivially crash the backend, but with appropriate misuse of pass-by-reference datatypes it is possible to read out arbitrary locations in the server process's memory, which could allow retrieving database content the user should not be able to see. Our thanks to Jeff Trout for the initial report. Security: CVE-2007-0556
2007-02-02Repair insufficiently careful type checking for SQL-language functions:Tom Lane
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. This is a significant security hole: not only can one trivially crash the backend, but with appropriate misuse of pass-by-reference datatypes it is possible to read out arbitrary locations in the server process's memory, which could allow retrieving database content the user should not be able to see. Our thanks to Jeff Trout for the initial report. Security: CVE-2007-0555
2007-02-01Fix broken markup.Tom Lane
2007-02-01Add "May/Can/Might" section to error message style guidlines, andBruce Momjian
"can't" -> "cannot" section.
2007-02-01Fix two more regression tests whose expected outputs were not updatedNeil Conway
for the recent may/might cleanup.
2007-02-01Mention file system replication as a high availability solution in theBruce Momjian
shared hardware section, and mention DRBD as a popular solution.
2007-02-01Typo fix.Tom Lane
2007-02-01Update some of the "expected" regression test results for Bruce'sNeil Conway
recent may/might cleanup, in the hopes that this will unbreak the buildfarm. Per report from Stefan Kaltenbrunner.
2007-02-01Fix plpgsql so that when a local variable has no initial-value expression,Tom Lane
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).
2007-02-01Add URL for:Bruce Momjian
o Add long file support for binary pg_dump output > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php
2007-02-01Wording cleanup for error messages. Also change can't -> cannot.Bruce Momjian
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01Fix broken markup.Neil Conway
2007-02-01Add 8.2.0 "Incomatibilities" documentation that pg_dump's -n and -tBruce Momjian
behavior has changed.
2007-02-01Chinese FAQ updateBruce Momjian
Daojing.Zhou
2007-02-01Update URL for function permission checksBruce Momjian
< http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php >
2007-02-01Add:Bruce Momjian
> > * Tighten function permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
2007-02-01Add:Bruce Momjian
> > * Tighten trigger permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
2007-02-01This patch adds documentation for the long-version parameters --usernameNeil Conway
and --password for pg_dump, pg_dumpall and pg_restore, per complaint by Michael Schmidt. Patch from Magnus Hagander.
generated by cgit v1.2.3 (git 2.46.0) at 2025-10-17 23:19:44 +0000