- 24 Apr, 2013 1 commit
- 
- 
Bruce Momjian authored
 
- 
- 23 Apr, 2013 2 commits
- 
- 
Bruce Momjian authoredErikjan Rijkers 
- 
Heikki Linnakangas authoredAdrian Schreyer 
 
- 
- 22 Apr, 2013 8 commits
- 
- 
Bruce Momjian authoredAlvaro Herrera 
- 
Bruce Momjian authored
- 
Heikki Linnakangas authoredThis is new in 9.3devel. 
- 
Bruce Momjian authored
- 
Bruce Momjian authoredAndres Freund 
- 
Peter Eisentraut authoredErwin Brandstetter 
- 
Peter Eisentraut authoredLANGUAGE 'plpgsql' no longer works. The single quotes need to be removed. Erwin Brandstetter 
- 
Bruce Momjian authoredSplit log shipping speed improvement and fail-over speed improvement items. Per request from Simon 
 
- 
- 21 Apr, 2013 5 commits
- 
- 
Bruce Momjian authored
- 
Bruce Momjian authoredAlready fixed in back branch. 
- 
Bruce Momjian authoredMove commit_delay, fix Zoltan's name, and adjust range type histogram text. 
- 
Bruce Momjian authored
- 
Bruce Momjian authoredTypo fix from David Fetter. 
 
- 
- 20 Apr, 2013 8 commits
- 
- 
Bruce Momjian authored
- 
Bruce Momjian authored
- 
Tom Lane authoredWhen creating or manipulating a cached plan for a transaction control command (particularly ROLLBACK), we must not perform any catalog accesses, since we might be in an aborted transaction. However, plancache.c busily saved or examined the search_path for every cached plan. If we were unlucky enough to do this at a moment where the path's expansion into schema OIDs wasn't already cached, we'd do some catalog accesses; and with some more bad luck such as an ill-timed signal arrival, that could lead to crashes or Assert failures, as exhibited in bug #8095 from Nachiket Vaidya. Fortunately, there's no real need to consider the search path for such commands, so we can just skip the relevant steps when the subject statement is a TransactionStmt. This is somewhat related to bug #5269, though the failure happens during initial cached-plan creation rather than revalidation. This bug has been there since the plan cache was invented, so back-patch to all supported branches. 
- 
Bruce Momjian authoredMore to go. 
- 
Bruce Momjian authoredForgotten in previous commit. 
- 
Bruce Momjian authoredNo links added yet. 
- 
Peter Eisentraut authoredsuggested by Jov 
- 
Peter Eisentraut authoredIn most cases, these were just references to the SQL standard in general. In a few cases, a contrast was made between SQL92 and later standards -- those have been kept unchanged. 
 
- 
- 19 Apr, 2013 4 commits
- 
- 
Tom Lane authoredIf an FDW fails to take special measures with a CurrentOfExpr, we will end up trying to execute it as an ordinary qual, which was being treated as a purely internal failure condition. Provide a more user-oriented error message for such cases. 
- 
Robert Haas authoredFabrízio de Royes Mello 
- 
Peter Eisentraut authoredOnly adjusted the user-exposed messages and documentation, not all source code comments. 
 
- 
- 17 Apr, 2013 4 commits
- 
- 
Bruce Momjian authoredWe might eventually allow checksum to no-checksum upgrades. 
- 
Robert Haas authoredKaiGai Kohei 
- 
Robert Haas authoredKaiGai Kohei, based on a suggestion from Álvaro Herrera 
- 
Peter Eisentraut authoredThe return type of PQgetssl() was changed from SSL* to void* a long time ago, but the documentation was not updated. 
 
- 
- 16 Apr, 2013 4 commits
- 
- 
Bruce Momjian authored
- 
Heikki Linnakangas authoredThis saves some memory from each index relcache entry. At least on a 64-bit machine, it saves just enough to shrink a typical relcache entry's memory usage from 2k to 1k. That's nice if you have a lot of backends and a lot of indexes. 
- 
Peter Eisentraut authoredWhen parse_hba_line's return type was changed from bool to a pointer, the MANDATORY_AUTH_ARG macro wasn't adjusted. 
- 
Andrew Dunstan authoredPer complaint from Hubert Depesz Lubaczewski. Catalog version bumped. 
 
- 
- 15 Apr, 2013 2 commits
- 
- 
Andrew Dunstan authoredPer gripe from Tom Lane. 
- 
Tom Lane authoredThe initial coding just descended the index if any of the target trigrams were possibly present at the next level down. But actually we can apply trigramsMatchGraph() so as to take advantage of AND requirements when there are some. The input data might contain false positive matches, but that can only result in a false positive result, not false negative, so it's safe to do it this way. Alexander Korotkov 
 
- 
- 14 Apr, 2013 2 commits
- 
- 
Peter Eisentraut authored
- 
Peter Eisentraut authoredThis changes the behavior of the start and stop actions to exit successfully if the server was already started or stopped. This changes the default behavior of the start action: Before, if the server was already running, it would print a message and succeed. Now, that situation will result in an error. When running in idempotent mode, no message is printed and pg_ctl exits successfully. It was considered to just make the idempotent behavior the default and only option, but pg_upgrade needs the old behavior. 
 
-