aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* In vacuumdb --help, call analyze "statistics", not "hints".Bruce Momjian2010-02-26
|
* Call output file typedefs.list; update README.Bruce Momjian2010-02-26
|
* Document pg_restore --jobs as a performance enhancement.Bruce Momjian2010-02-26
|
* Update pgindent instructions.Bruce Momjian2010-02-26
|
* pgindent run for 9.0Bruce Momjian2010-02-26
|
* Add pgindent typedefs file to CVS.Bruce Momjian2010-02-26
|
* Update pgindent instructions to avoid changes to flex output files.Bruce Momjian2010-02-26
|
* Remove 'emphasis' markup inside literal; not allowed.Bruce Momjian2010-02-26
|
* Document that after triggers that need to see changed rows should not beBruce Momjian2010-02-25
| | | | marked stable.
* Allow predicate_refuted_by() to deduce that NOT A refutes A.Tom Lane2010-02-25
| | | | | | | | | | | | | | | | | | | | | We had originally made the stronger assumption that NOT A refutes any B if B implies A, but this fails in three-valued logic, because we need to prove B is false not just that it's not true. However the logic does go through if B is equal to A. Recognizing this limited case is enough to handle examples that arise when we have simplified "bool_var = true" or "bool_var = false" to just "bool_var" or "NOT bool_var". If we had not done that simplification then the btree-operator proof logic would have been able to prove that the expressions were contradictory, but only for identical expressions being compared to the constants; so handling identical A and B covers all the same cases. The motivation for doing this is to avoid unexpected asymmetrical behavior when a partitioned table uses a boolean partitioning column, as in today's gripe from Dominik Sander. Back-patch to 8.2, which is as far back as predicate_refuted_by attempts to do anything at all with NOTs.
* Document clearly the meaning of none/all for log_statements.Bruce Momjian2010-02-25
|
* Add C comment that do_to_timestamp() lacks error checking.Bruce Momjian2010-02-25
|
* Clearly document that timestamp alone means timestamp without timezone,Bruce Momjian2010-02-25
| | | | per SQL standard, and mention 7.3 behavior at the end.
* Add configuration parameter ssl_renegotiation_limit to controlMagnus Hagander2010-02-25
| | | | | | | | how often we do SSL session key renegotiation. Can be set to 0 to disable renegotiation completely, which is required if a broken SSL library is used (broken patches to CVE-2009-3555 a known cause) or when using a client library that can't do renegotiation.
* Fix typos, per Richard HuxtonMagnus Hagander2010-02-25
|
* Clarify that the connection string for primary_conninfo is in the sameHeikki Linnakangas2010-02-25
| | | | format as in PQconnectdb(). As pointed out by Thom Brown.
* Fix typo.Heikki Linnakangas2010-02-25
|
* Small streaming replication document improvements. Be more explicit thatHeikki Linnakangas2010-02-25
| | | | it's asynchronous.
* Fix streaming replication starting at the very first WAL segment.Heikki Linnakangas2010-02-25
| | | | Per complaint from Greg Stark.
* Improve warning about creating nested named subroutines in plperl.Tom Lane2010-02-25
| | | | Per discussion.
* Make pg_stop_backup's reporting a bit more verbose in hopes of makingTom Lane2010-02-25
| | | | | | error cases less intimidating for novices. Per discussion. Greg Smith
* Allow zero-dimensional (ie, empty) arrays in contrib/ltree operations.Tom Lane2010-02-24
| | | | | | | | | | | | | | | | The main motivation for changing this is bug #4921, in which it's pointed out that it's no longer safe to apply ltree operations to the result of ARRAY(SELECT ...) if the sub-select might return no rows. Before 8.3, the ARRAY() construct would return NULL, which might or might not be helpful but at least it wouldn't result in an error. Now it returns an empty array which results in a failure for no good reason, since the ltree operations are all perfectly capable of dealing with zero-element arrays. As far as I can find, these ltree functions are the only places where zero array dimensionality is rejected unnecessarily. Back-patch to 8.3 to prevent behavioral regression of queries that worked in older releases.
* Document that pg_restore -t can use -n for its schema qualification.Bruce Momjian2010-02-24
|
* Revert removal of pre-7.4 documenation behavior mentions.Bruce Momjian2010-02-24
|
* Remove stray semicolon, per report from strkAlvaro Herrera2010-02-24
|
* Remove useless codes to initialize TupleDesc from dblink_exec.Itagaki Takahiro2010-02-24
|
* Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldestBruce Momjian2010-02-24
| | | | supported release.
* Fix patch for printing backend and pg_dump versions so that it works inTom Lane2010-02-24
| | | | | a desirable fashion in archive-dump cases, ie you should get the pg_dump version not the pg_restore version.
* Un-break pg_dump for the case of zero-column tables.Tom Lane2010-02-24
| | | | | | This was evidently broken by the CREATE TABLE OF TYPE patch. It would have been noticed if anyone had bothered to try dumping and restoring the regression database ...
* Use CREATE OR REPLACE LANGUAGE in pg_dump to avoid the need for a couple ofTom Lane2010-02-24
| | | | | significantly uglier kluges that were working around the change in plpgsql's preinstalled status.
* Make pg_regress use CREATE OR REPLACE LANGUAGE, so that --load-languageTom Lane2010-02-24
| | | | | | will work whether or not the specified language is preinstalled. This responds to some complaints about having to change test scripts because plpgsql is preinstalled as of 9.0.
* Add an OR REPLACE option to CREATE LANGUAGE.Tom Lane2010-02-23
| | | | | | | | | | | | | | | This operates in the same way as other CREATE OR REPLACE commands, ie, it replaces everything but the ownership and ACL lists of an existing entry, and requires the caller to have owner privileges for that entry. While modifying an existing language has some use in development scenarios, in typical usage all the "replaced" values come from pg_pltemplate so there will be no actual change in the language definition. The reason for adding this is mainly to allow programs to ensure that a language exists without triggering an error if it already does exist. This commit just adds and documents the new option. A followon patch will use it to clean up some unpleasant cases in pg_dump and pg_regress.
* Modify freebsd start script to just exit 0 with message.Bruce Momjian2010-02-23
|
* Update startup scripts for Linux and FreeBSD.Bruce Momjian2010-02-23
| | | | Kevin Grittner
* Have pg_dump (-v) verbose mode output the pg_dump and server versions inBruce Momjian2010-02-23
| | | | | | text output mode, like we do in custom output mode. Jim Cox
* Revert recent COPY manual change about encoding; add mention of "server".Bruce Momjian2010-02-23
|
* Fix configure's regexp for extracting the Perl version number from perl -vTom Lane2010-02-23
| | | | | | | output. Per bug #5339, Perl 5.11 has changed the format of that output enough to break the previous coding. Alex Hunsaker
* Clarify statements about tar archive format.Tom Lane2010-02-23
|
* Minor style policing for error messages in pg_dump tar code. Notably, changeTom Lane2010-02-23
| | | | | | | "dumping data out of order is not supported" to "restoring data out of order is not supported", because you get that error during pg_restore not pg_dump. Also fix some comments that didn't look so good after being pgindented as perhaps they did originally.
* Revert recent change of to_char('HH12') handling for intervals; insteadBruce Momjian2010-02-23
| | | | improve documentation, and add C comment.
* Secondary patch to fix interval to_char() for "HH" where hours >= 12.Bruce Momjian2010-02-23
|
* Some platforms reject fsync() on files opened O_RDONLY.Tom Lane2010-02-23
|
* Make documentation more direct about the handling of COPY files based onBruce Momjian2010-02-23
| | | | the client encoding.
* Document that expression indexes that call functions allow function-levelBruce Momjian2010-02-23
| | | | statistics.
* Supress convertion of zero hours to '12' for intervals when usingBruce Momjian2010-02-23
| | | | | | | | | | | | | | to_char with HH, e.g. to_char(interval '0d 0h 12m 44s', 'DD HH24 MI SS'); now returns: 00 00 12 44 not: 00 12 12 44
* Update pg_restore documentation to show new pg_restore custom listingBruce Momjian2010-02-23
| | | | | | format. Pavel Golub
* Remove long-commented-out paragraph in documentation about functionBruce Momjian2010-02-22
| | | | inheritance in create table, per Andrew Dunstan.
* Document that pg_ctl cares about the PGHOST environment variable.Bruce Momjian2010-02-22
|
* Revert configure warning to use "official distribution".Bruce Momjian2010-02-22
|
* Remove protocol documentation paragraph about environment variableBruce Momjian2010-02-22
| | | | passing being "covered elsewhere", per Dave Page.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-08 02:20:05 +0000