aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* 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.
* Use the term "bundled distribution" instead of "official distribution" inBruce Momjian2010-02-22
| | | | configure warnings.
* Briefly document in two places that pg_dump and pg_dumpall cannot beBruce Momjian2010-02-22
| | | | used for continuous archiving.
* Let's try forcing errno to zero before issuing fsync. The current buildfarmTom Lane2010-02-22
| | | | | results claiming EBADF seem improbable enough that I'm not convinced fsync is really returning that --- could it be failing to set errno at all?
* Adjust pg_fsync_writethrough so that it will set errno when failingTom Lane2010-02-22
| | | | | | | on a platform that doesn't support this operation. The former coding would allow an unrelated errno to be reported, which would be quite misleading. Not sure if this has anything to do with the current buildfarm failures, but it's certainly bogus as-is.
* Move documentation of all recovery.conf option to a new chapter.Heikki Linnakangas2010-02-22
| | | | | They used to be scattered between the "backup and restore" and "streaming replication" chapters.
* Fix multiple copy and paste-o's. No wonder this code didn't work.Tom Lane2010-02-22
|
* Oops, don't forget to rewind the directory before scanning it to fsync files ↵Greg Stark2010-02-22
| | | | in CREATE DATABASE
* Adjust sample auto-explain output to reflect query text inclusion.Andrew Dunstan2010-02-20
|
* Clean up handling of XactReadOnly and RecoveryInProgress checks.Tom Lane2010-02-20
| | | | | | | | | | | | | | | | | | Add some checks that seem logically necessary, in particular let's make real sure that HS slave sessions cannot create temp tables. (If they did they would think that temp tables belonging to the master's session with the same BackendId were theirs. We *must* not allow myTempNamespace to become set in a slave session.) Change setval() and nextval() so that they are only allowed on temp sequences in a read-only transaction. This seems consistent with what we allow for table modifications in read-only transactions. Since an HS slave can't have a temp sequence, this also provides a nicer cure for the setval PANIC reported by Erik Rijkers. Make the error messages more uniform, and have them mention the specific command being complained of. This seems worth the trifling amount of extra code, since people are likely to see such messages a lot more than before.
* Make 'include_realm' ordering consistent in the docs, to match recentBruce Momjian2010-02-20
| | | | doc change.
* Clarify documentation about username mapping when authenticating withBruce Momjian2010-02-20
| | | | | | GSSAPI or Kerberos. Ian Turner
* Document that many solid-state drives have volatile write-back caches.Bruce Momjian2010-02-20
|
* Copy editing of Hot Standby docs. Some clarifications, additionSimon Riggs2010-02-20
| | | | of missing items and minor edits.
* Reduce the rescan cost estimate for Materialize nodes to cpu_operator_cost perTom Lane2010-02-19
| | | | | | | | | | | | | | | | tuple, instead of the former cpu_tuple_cost. It is sane to charge less than cpu_tuple_cost because Materialize never does any qual-checking or projection, so it's got less overhead than most plan node types. In particular, we want to have the same charge here as is charged for readout in cost_sort. That avoids the problem recently exhibited by Teodor wherein the planner prefers a useless sort over a materialize step in a context where a lot of rescanning will happen. The rescan costs should be just about the same for both node types, so make their estimates the same. Not back-patching because all of the current logic for rescan cost estimates is new in 9.0. The old handling of rescans is sufficiently not-sane that changing this in that structure is a bit pointless, and might indeed cause regressions.
* Revert version stamping in wrong branchPeter Eisentraut2010-02-19
|
* Version stamp 9.0alpha4Peter Eisentraut2010-02-19
|
* Document --version and --help options for all client applications (theyBruce Momjian2010-02-19
| | | | | | all support it). Per report from Josh Kupershmidt
* Small corrections to message output targets in pg_ctlPeter Eisentraut2010-02-19
| | | | | | | - The message "server stopped" should be affected by the -s option, just like "server started" already was. - The message "could not start server" should consistently go to stderr.
* Don't use O_DIRECT when writing WAL files if archiving or streaming isHeikki Linnakangas2010-02-19
| | | | | | | | | | enabled. Bypassing the kernel cache is counter-productive in that case, because the archiver/walsender process will read from the WAL file soon after it's written, and if it's not cached the read will cause a physical read, eating I/O bandwidth available on the WAL drive. Also, walreceiver process does unaligned writes, so disable O_DIRECT in walreceiver process for that reason too.
* Forbid setval() during recovery. This prevents the PANIC reported byHeikki Linnakangas2010-02-19
| | | | Erik Rijkers. Patch by Andres Freund.
* First pass over client applications documentation proofreading.Bruce Momjian2010-02-19
| | | | gabrielle
* Remove mention that binary distributions pre-compile the tutorial files.Bruce Momjian2010-02-19
|
* Fix STOP WAL LOCATION in backup history files no to return the nextItagaki Takahiro2010-02-19
| | | | | | | | | | | segment of XLOG_BACKUP_END record even if the the record is placed at a segment boundary. Furthermore the previous implementation could return nonexistent segment file name when the boundary is in segments that has "FE" suffix; We never use segments with "FF" suffix. Backpatch to 8.0, where hot backup was introduced. Reported by Fujii Masao.
* Translation updates for 9.0alpha4Peter Eisentraut2010-02-19
|
* Preliminary release notes for 9.0alpha4Peter Eisentraut2010-02-19
|
* Hot Standby documentation updatesBruce Momjian2010-02-19
| | | | Greg Smith
* Volatile-ize all five places where we expect a PG_TRY block to restoreTom Lane2010-02-18
| | | | | | old memory context in plpython. Before only one of them was marked volatile, but per report from Zdenek Kotala, some compilers do the wrong thing here.
* Provide some rather hokey ways for EXPLAIN to print FieldStore and assignmentTom Lane2010-02-18
| | | | | | | | | | | | | | | | | | ArrayRef expressions that are not in the immediate context of an INSERT or UPDATE targetlist. Such cases never arise in stored rules, so ruleutils.c hadn't tried to handle them. However, they do occur in the targetlists of plans derived from such statements, and now that EXPLAIN VERBOSE tries to print targetlists, we need some way to deal with the case. I chose to represent an assignment ArrayRef as "array[subscripts] := source", which is fairly reasonable and doesn't omit any information. However, FieldStore is problematic because the planner will fold multiple assignments to fields of the same composite column into one FieldStore, resulting in a structure that is hard to understand at all, let alone display comprehensibly. So in that case I punted and just made it print the source expression(s). Backpatch to 8.4 --- the lack of functionality exists in older releases, but doesn't seem to be important for lack of anything that would call it.
* Fix ExecEvalArrayRef to pass down the old value of the array element or sliceTom Lane2010-02-18
| | | | | | | | | | | | | being assigned to, in case the expression to be assigned is a FieldStore that would need to modify that value. The need for this was foreseen some time ago, but not implemented then because we did not have arrays of composites. Now we do, but the point evidently got overlooked in that patch. Net result is that updating a field of an array element doesn't work right, as illustrated if you try the new regression test on an unpatched backend. Noted while experimenting with EXPLAIN VERBOSE, which has also got some issues in this area. Backpatch to 8.3, where arrays of composites were introduced.
* Fix pq_getbyte_if_available() function. It was confused on what itHeikki Linnakangas2010-02-18
| | | | | returns if no data is immediately available. Patch by me with numerous fixes from Fujii Masao and Magnus Hagander.
* date_recv should accept infinities.Itagaki Takahiro2010-02-18
| | | | Reported by James William Pye.
* Add missing close tag.Bruce Momjian2010-02-18
|
* Wordsmithing of HS and SR documentation, with some wording improvementsBruce Momjian2010-02-18
| | | | from Erik Rijkers too.
* Force READY portals into FAILED state when a transaction or subtransactionTom Lane2010-02-18
| | | | | | | | | | | is aborted, if they were created within the failed xact. This prevents ExecutorEnd from being run on them, which is a good idea because they may contain references to tables or other objects that no longer exist. In particular this is hazardous when auto_explain is active, but it's really rather surprising that nobody has seen an issue with this before. I'm back-patching this to 8.4, since that's the first version that contains auto_explain or an ExecutorEnd hook, but I wonder whether we shouldn't back-patch further.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 02:32:16 +0000