- 21 10月, 2008 7 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
error messages where the type existence is established.
-
由 Peter Eisentraut 提交于
alongside our traditional syntax.
-
由 Alvaro Herrera 提交于
knowledge of page layout. Stolen from Jonah Harris' CRC patch
-
由 Alvaro Herrera 提交于
Zdenek Kotala.
-
由 Alvaro Herrera 提交于
This patch eliminates the marking of subtransactions as SUBCOMMITTED in pg_clog during their commit; instead they remain in-progress until main transaction commit. At main transaction commit, the commit protocol is atomic-by-page instead of one transaction at a time. To avoid a race condition with some subtransactions appearing committed before others in the case where they span more than one pg_clog page, we conserve the logic that marks them subcommitted before marking the parent committed. Simon Riggs with minor help from me
-
- 20 10月, 2008 6 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
dropped or it was a mistake.
-
由 Peter Eisentraut 提交于
-
由 Teodor Sigaev 提交于
Per Tom's comment. Also revome useless GISTScanOpaque->flags field.
-
由 Peter Eisentraut 提交于
supported, to the extent that LOBs, arrays, and multisets are supported.
-
由 Peter Eisentraut 提交于
-
- 18 10月, 2008 11 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
(I'm leaving GiST/GIN cleanup to Teodor.)
-
由 Alvaro Herrera 提交于
formatted_start_time.
-
由 Tom Lane 提交于
scanning; GiST and GIN do not, and it seems like too much trouble to make them do so. By teaching ExecSupportsBackwardScan() about this restriction, we ensure that the planner will protect a scroll cursor from the problem by adding a Materialize node. In passing, fix another longstanding bug in the same area: backwards scan of a plan with set-returning functions in the targetlist did not work either, since the TupFromTlist expansion code pays no attention to direction (and has no way to run a SRF backwards anyway). Again the fix is to make ExecSupportsBackwardScan check this restriction. Also adjust the index AM API specification to note that mark/restore support is unnecessary if the AM can't produce ordered output.
-
由 Tom Lane 提交于
set_rel_width(). The code had been catering for the possibility of different varnos in the relation targetlist, but this is impossible for a base relation (and if it were possible, putting all the widths in the same RelOptInfo would be wrong anyway).
-
由 Tom Lane 提交于
-
由 Teodor Sigaev 提交于
several fragments a-la Google. Sushant Sinha <sushant354@gmail.com>
-
由 Teodor Sigaev 提交于
Patch from Sushant Sinha <sushant354@gmail.com> http://archives.postgresql.org/pgsql-hackers/2008-07/msg00785.php
-
由 Teodor Sigaev 提交于
is NULL but SK_SEARCHNULL is not set. Add checking IS NULL of keys to set during key initialization. If key is NULL and SK_SEARCHNULL is not set then nothnig can be satisfied. With assert-enabled compilation that causes coredump. Bug was introduced in 8.3 by support of IS NULL index scan.
-
- 17 10月, 2008 1 次提交
-
-
由 Neil Conway 提交于
In the previous coding, the list of columns that needed to be hashed on was allocated in the per-query context, but we reallocated every time the Agg node was rescanned. Since this information doesn't change over a rescan, just construct the list of columns once during ExecInitAgg().
-
- 16 10月, 2008 2 次提交
-
-
由 Tom Lane 提交于
ITAGAKI Takahiro
-
由 Tom Lane 提交于
according to the TupleDesc's natts, not the number of physical columns in the tuple. The previous coding would do the wrong thing in cases where natts is different from the tuple's column count: either incorrectly report error when it should just treat the column as null, or actually crash due to indexing off the end of the TupleDesc's attribute array. (The second case is probably not possible in modern PG versions, due to more careful handling of inheritance cases than we once had. But it's still a clear lack of robustness here.) The incorrect error indication is ignored by all callers within the core PG distribution, so this bug has no symptoms visible within the core code, but it might well be an issue for add-on packages. So patch all the way back.
-
- 15 10月, 2008 5 次提交
-
-
由 Tom Lane 提交于
lengthof(SysAtt) not FirstLowInvalidHeapAttributeNumber, for consistency with the other uses of the SysAtt array, and to make it clearer that it doesn't walk off the end of that array.
-
由 Tom Lane 提交于
Formerly, the lack of any opclasses that could accept such data was enough of a defense, but now with a "record" opclass we need to check more carefully. (You can still use that opclass for an index, but you have to store a named composite type not an anonymous one.)
-
由 Tom Lane 提交于
pointers. This is only a whitespace change, which ought to be ignored by regression testing, but for some reason buildfarm member spoonbill doesn't like it.
-
由 Alvaro Herrera 提交于
by renaming the new copies after the catalog games.
-
由 Tom Lane 提交于
the timestamp types. Turns out this doesn't even reduce the available range of dates, since the restriction to dates that work for Julian-date arithmetic is much tighter than the int32 range anyway. Per a longstanding TODO item.
-
- 14 10月, 2008 6 次提交
-
-
由 Tom Lane 提交于
returning a failure code that none of its callers bothered to check for.
-
由 Michael Meskes 提交于
-
由 Heikki Linnakangas 提交于
fsync requests. This should fix the installcheck failure of the buildfarm member "kudu".
-
由 Tom Lane 提交于
depth-first search order. Upon close reading of SQL:2008, it seems that the spec's SEARCH DEPTH FIRST and SEARCH BREADTH FIRST options do not actually guarantee any particular result order: what they do is provide a constructed column that the user can then sort on in the outer query. So this is actually just as much functionality ...
-
由 Tom Lane 提交于
detection.
-
由 Tom Lane 提交于
pseudo-type record[] to represent arrays of possibly-anonymous composite types. Since composite datums carry their own type identification, no extra knowledge is needed at the array level. The main reason for doing this right now is that it is necessary to support the general case of detection of cycles in recursive queries: if you need to compare more than one column to detect a cycle, you need to compare a ROW() to an array built from ROW()s, at least if you want to do it as the spec suggests. Add some documentation and regression tests concerning the cycle detection issue.
-
- 13 10月, 2008 2 次提交