aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Fix documentation reference to "above" examplePeter Eisentraut2011-06-04
| | | | found by Thom Brown
* More ECPG documentation fixesPeter Eisentraut2011-06-04
| | | | Marc Cousin
* ECPG documentation fixPeter Eisentraut2011-06-04
| | | | Marc Cousin, Satoshi Nagayasu
* Truncate id to <=44 charactersPeter Eisentraut2011-06-03
| | | | | | | | This is the original DocBook SGML limit, but apparently most installations have changed it or ignore it, which is why few people have run into this problem. pointed out by Brendan Jurd
* Use proper SGML doc entities rather than angle-brackets.Bruce Momjian2011-06-02
| | | | Marco Nenciarini
* Sort COMMENT synopsis and add more examplesPeter Eisentraut2011-06-03
| | | | Josh Kupershmidt
* Some copy editing of the release notesPeter Eisentraut2011-06-01
|
* Protect GIST logic that assumes penalty values can't be negative.Tom Lane2011-05-31
| | | | | | | | | | Apparently sane-looking penalty code might return small negative values, for example because of roundoff error. This will confuse places like gistchoose(). Prevent problems by clamping negative penalty values to zero. (Just to be really sure, I also made it force NaNs to zero.) Back-patch to all supported branches. Alexander Korotkov
* Use entities to encode non-ASCII characters in SGML documentationPeter Eisentraut2011-05-31
| | | | | This has already been the case for the most part; just some cases had slipped through.
* Replace use of credential control messages with getsockopt(LOCAL_PEERCRED).Tom Lane2011-05-31
| | | | | | | | | | | | | | | | | | | | | | | | It turns out the reason we hadn't found out about the portability issues with our credential-control-message code is that almost no modern platforms use that code at all; the ones that used to need it now offer getpeereid(), which we choose first. The last holdout was NetBSD, and they added getpeereid() as of 5.0. So far as I can tell, the only live platform on which that code was being exercised was Debian/kFreeBSD, ie, FreeBSD kernel with Linux userland --- since glibc doesn't provide getpeereid(), we fell back to the control message code. However, the FreeBSD kernel provides a LOCAL_PEERCRED socket parameter that's functionally equivalent to Linux's SO_PEERCRED. That is both much simpler to use than control messages, and superior because it doesn't require receiving a message from the other end at just the right time. Therefore, add code to use LOCAL_PEERCRED when necessary, and rip out all the credential-control-message code in the backend. (libpq still has such code so that it can still talk to pre-9.1 servers ... but eventually we can get rid of it there too.) Clean up related autoconf probes, too. This means that libpq's requirepeer parameter now works on exactly the same platforms where the backend supports peer authentication, so adjust the documentation accordingly.
* Don't recommend upgrading to latest available Windows SDKMagnus Hagander2011-05-30
| | | | | | We only support up to version 7.0, so don't recommend upgrading past it. The rest of the documentation around this was already updated, but one spot was missed.
* Add pg_basebackup -z option for compression with default levelPeter Eisentraut2011-05-30
|
* Correct description of log_connections and log_disconnectionsPeter Eisentraut2011-05-29
| | | | | | | The previous claim when these parameters could be changed was incorrect. Fujii Masao
* Allow pg_basebackup compressed tar output to stdoutPeter Eisentraut2011-05-29
|
* Drop "meaning" column from error code tablePeter Eisentraut2011-05-28
| | | | | This is currently the same as the condition name, so it doesn't add any value, only clutter.
* Put options in some sensible orderPeter Eisentraut2011-05-25
| | | | | | | For the --help output and reference pages of pg_dump, pg_dumpall, pg_restore, put the options in some consistent, mostly alphabetical, and consistent order, rather than newest option last or something like that.
* Put lists in sensible orderPeter Eisentraut2011-05-22
|
* Put documentation of backslash commands back in alphabetical orderPeter Eisentraut2011-05-22
|
* Clarify the documentation of the --with-ossp-uuid optionPeter Eisentraut2011-05-22
|
* Rename pg_dump --no-security-label to --no-security-labelsPeter Eisentraut2011-05-19
| | | | Other similar options also use the plural form.
* Remove obsolete commentPeter Eisentraut2011-05-19
|
* Spell checking and markup refinementPeter Eisentraut2011-05-19
|
* /contrib/foo -> contrib/fooPeter Eisentraut2011-05-19
| | | | | Since contrib is a relative directory specification, a leading slash is inappropriate.
* Remove redundant privilege doc sentences.Bruce Momjian2011-05-16
|
* Allow pg_upgrade to honor libpq environment variables. Add 'local'Bruce Momjian2011-05-16
| | | | checks for PGHOST and PGHOSTADDR.
* More cleanup of FOREIGN TABLE permissions handling.Robert Haas2011-05-13
| | | | | | | | | This commit fixes psql, pg_dump, and the information schema to be consistent with the backend changes which I made as part of commit be90032e0d1cf473bdd99aee94218218f59f29f1, and also includes a related documentation tweak. Shigeru Hanada, with slight adjustment.
* Be more explicit about the meaning of the change in standard_conforming_strings.Tom Lane2011-05-10
|
* Mention "backslash" escape processing change in 9.1 release notes.Bruce Momjian2011-05-10
|
* Add some punctuationPeter Eisentraut2011-05-10
|
* Put options in more alphabetical orderPeter Eisentraut2011-05-10
|
* Adjust documentation with respect to "unknown" timezone setting.Tom Lane2011-05-10
| | | | | | The recent cleanup of GUC assign hooks got rid of the kludge of using "unknown" as a magic value for timezone and log_timezone. But I forgot to update the documentation to match, as noted by Martin Pitt.
* Documentation cleanup for the possible values of the datatype 'boolean'.Bruce Momjian2011-05-09
|
* Update documentation to state there is three-value logic, notBruce Momjian2011-05-09
| | | | | | | three-value boolean logic. Backpatch to 9.0.X since we just got another bug report about this today.
* Add xreflabels to /contrib manuals so links appear correct. Also updateBruce Momjian2011-05-07
| | | | README.links to explain xref properly.
* Add missing documention connecting word.Bruce Momjian2011-05-07
|
* Fix typos in SECURITY LABEL documentation.Robert Haas2011-05-06
| | | | KaiGai Kohei
* Improve style of generate_history.pl Perl script.Bruce Momjian2011-05-05
|
* Include unary plus in the Operator Precedence table.Tom Lane2011-05-04
| | | | | | | Per gripe from Grzegorz Szpetkowski. Also, change the subsection heading from "Lexical Precedence" (which is a contradiction in terms) to "Operator Precedence".
* Link some tables into the surrounding text by their idPeter Eisentraut2011-05-04
|
* Update obsolete mention of Sequoia, now known as TungstenAlvaro Herrera2011-05-03
| | | | | | Per http://joomla.aws.continuent.com/community/lab-projects/sequoia Greg Smith
* Improve description of read/write traffic scalabilityAlvaro Herrera2011-05-03
| | | | Greg Smith, after a suggestion of James Bruce
* Add ID attribute to some sect2's missing itAlvaro Herrera2011-05-02
| | | | David Fetter
* Update some ALTER USER cross-references to ALTER ROLEAlvaro Herrera2011-05-02
| | | | Greg Smith
* Small cleanup of spacing in verbatim DocBook elementsPeter Eisentraut2011-05-02
|
* The arguments to pg_ctl kill are not optional - remove brackets in the docs.Heikki Linnakangas2011-04-28
| | | | Fujii Masao
* Make a quick copy-editing pass over the 9.1 release notes.Tom Lane2011-04-27
| | | | | | | Also remove the material about this being an alpha release. The notes still need a lot of work, but they're more or less presentable as a beta version now.
* Add comments about the need to avoid uninitialized bits in datatype values.Tom Lane2011-04-27
| | | | | | | | There was already one recommendation in the documentation about writing C functions to ensure padding bytes are zeroes, but make it stronger. Also fix an example that was still using direct assignment to a varlena length word, which no longer works since the varvarlena changes.
* Doc wording improvement for NUMERIC limit paragraph.Bruce Momjian2011-04-27
|
* Reword documentation for NUMERIC with no specified precision.Bruce Momjian2011-04-26
|
* Clarify that a non-specified precision NUMERIC has a very high range.Bruce Momjian2011-04-26
|