- 27 4月, 2013 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
ORDER BY expressions were being treated the same as regular aggregate arguments for purposes of collation determination, but really they should not affect the aggregate's collation at all; only collations of the aggregate's regular arguments should affect it. In many cases this mistake would lead to incorrectly throwing a "collation conflict" error; but in some cases the corrected code will silently assign a different collation to the aggregate than before, for example agg(foo ORDER BY bar COLLATE "x") which will now use foo's collation rather than "x" for the aggregate. Given this risk and the lack of field complaints about the issue, it doesn't seem prudent to back-patch. In passing, rearrange code in assign_collations_walker so that we don't need multiple copies of the standard logic for computing collation of a node with children. (Previously, CaseExpr duplicated the standard logic, and we would have needed a third copy for Aggref without this change.) Andrew Gierth and David Fetter
-
由 Joe Conway 提交于
Ensure that user created rows in extension tables get dumped if the table is explicitly requested, either with a -t/--table switch of the table itself, or by -n/--schema switch of the schema containing the extension table. Patch reviewed by Vibhor Kumar and Dimitri Fontaine. Backpatched to 9.1 when the extension management facility was added.
-
- 26 4月, 2013 2 次提交
-
-
由 Robert Haas 提交于
There's probably no real bug here at present, so not backpatching. But it seems good to make these bits consistent with the rest of libpq, so as to avoid future surprises. Patch by me. Review by Tom Lane.
-
由 Tom Lane 提交于
There was a high probability of two or more concurrent C.I.C. commands deadlocking just before completion, because each would wait for the others to release their reference snapshots. Fix by releasing the snapshot before waiting for other snapshots to go away. Per report from Paul Hinze. Back-patch to all active branches.
-
- 25 4月, 2013 5 次提交
-
-
由 Heikki Linnakangas 提交于
Peter Geoghegan
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
Erwin Brandstetter and Pavel Stěhule
-
由 Heikki Linnakangas 提交于
On non-Windows systems, sys/time.h was pulled in by portability/instr_time.h, which pulled in time.h. We certainly should include time.h directly, since we're using time(2), but the indirect include masked the problem on most platforms. Andres Freund
-
- 24 4月, 2013 4 次提交
-
-
由 Kevin Grittner 提交于
This was due to incomplete implementation of rowcount reporting for RMV, which was due to initial waffling on whether it should be provided. It seems unlikely to be a useful or universally available number as more sophisticated techniques for maintaining matviews are added, so remove the partial support rather than completing it. Per report of Jeevan Chalke, but with a different fix
-
由 Simon Riggs 提交于
Continue to allow a request for synchronous checkpoints as a mechanism in case of problems.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Erikjan Rijkers
-
- 23 4月, 2013 5 次提交
-
-
由 Heikki Linnakangas 提交于
Adrian Schreyer
-
由 Bruce Momjian 提交于
Alvaro Herrera
-
由 Bruce Momjian 提交于
-
由 Heikki Linnakangas 提交于
This is new in 9.3devel.
-
由 Bruce Momjian 提交于
-
- 22 4月, 2013 4 次提交
-
-
由 Bruce Momjian 提交于
Andres Freund
-
由 Peter Eisentraut 提交于
Erwin Brandstetter
-
由 Peter Eisentraut 提交于
LANGUAGE 'plpgsql' no longer works. The single quotes need to be removed. Erwin Brandstetter
-
由 Bruce Momjian 提交于
Split log shipping speed improvement and fail-over speed improvement items. Per request from Simon
-
- 21 4月, 2013 12 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Already fixed in back branch.
-
由 Bruce Momjian 提交于
Move commit_delay, fix Zoltan's name, and adjust range type histogram text.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Typo fix from David Fetter.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
When 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 提交于
More to go.
-
由 Bruce Momjian 提交于
Forgotten in previous commit.
-
由 Bruce Momjian 提交于
No links added yet.
-
由 Peter Eisentraut 提交于
suggested by Jov
-
- 20 4月, 2013 3 次提交
-
-
由 Peter Eisentraut 提交于
In 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.
-
由 Tom Lane 提交于
If 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.
-
- 19 4月, 2013 2 次提交
-
-
由 Robert Haas 提交于
Fabrízio de Royes Mello
-
由 Peter Eisentraut 提交于
Only adjusted the user-exposed messages and documentation, not all source code comments.
-