aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* SQL:2008 alternative syntax for LIMIT/OFFSET:Peter Eisentraut2008-10-22
| | | | OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS} ONLY
* Add a concept of "placeholder" variables to the planner. These are variablesTom Lane2008-10-21
| | | | | | | | | | | | | | | | | | | that represent some expression that we desire to compute below the top level of the plan, and then let that value "bubble up" as though it were a plain Var (ie, a column value). The immediate application is to allow sub-selects to be flattened even when they are below an outer join and have non-nullable output expressions. Formerly we couldn't flatten because such an expression wouldn't properly go to NULL when evaluated above the outer join. Now, we wrap it in a PlaceHolderVar and arrange for the actual evaluation to occur below the outer join. When the resulting Var bubbles up through the join, it will be set to NULL if necessary, yielding the correct results. This fixes a planner limitation that's existed since 7.1. In future we might want to use this mechanism to re-introduce some form of Hellerstein's "expensive functions" optimization, ie place the evaluation of an expensive function at the most suitable point in the plan tree.
* Clean regression.outPeter Eisentraut2008-10-21
|
* Use format_type_be() instead of TypeNameToString() for some more user-facingPeter Eisentraut2008-10-21
| | | | error messages where the type existence is established.
* Allow SQL:2008 syntax ALTER TABLE ... ALTER COLUMN ... SET DATA TYPEPeter Eisentraut2008-10-21
| | | | alongside our traditional syntax.
* Properly access a buffer's LSN using existing access macros instead of abusingAlvaro Herrera2008-10-20
| | | | | | knowledge of page layout. Stolen from Jonah Harris' CRC patch
* These functions no longer return a value, per complaint from gothic_moth viaAlvaro Herrera2008-10-20
| | | | Zdenek Kotala.
* Rework subtransaction commit protocol for hot standby.Alvaro Herrera2008-10-20
| | | | | | | | | | | | 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
* Remove support of backward scan in GiST. Per discussionTeodor Sigaev2008-10-20
| | | | http://archives.postgresql.org/pgsql-hackers/2008-10/msg00857.php
* SQL 200N -> SQL:2003Peter Eisentraut2008-10-20
|
* Feature T411 is not found in SQL:2003 or 2008 anymore, so it must have beenPeter Eisentraut2008-10-20
| | | | dropped or it was a mistake.
* Feature T152 "DISTINCT predicate with negation" is supported.Peter Eisentraut2008-10-20
|
* Remove mark/restore support in GIN and GiST indexes.Teodor Sigaev2008-10-20
| | | | | Per Tom's comment. Also revome useless GISTScanOpaque->flags field.
* Feature F402 "Named column joins for LOBs, arrays, and multisets" isPeter Eisentraut2008-10-20
| | | | supported, to the extent that LOBs, arrays, and multisets are supported.
* AS is no longer required in SELECT listPeter Eisentraut2008-10-20
|
* Fix broken SQL features data, per buildfarm results.Tom Lane2008-10-18
|
* Update feature list for SQL:2008.Peter Eisentraut2008-10-18
|
* Remove useless mark/restore support in hash index AM, per discussion.Tom Lane2008-10-17
| | | | (I'm leaving GiST/GIN cleanup to Teodor.)
* Refactor some duplicate code to set up formatted_log_time andAlvaro Herrera2008-10-17
| | | | formatted_start_time.
* Add a new column to pg_am to specify whether an index AM supports backwardTom Lane2008-10-17
| | | | | | | | | | | | | | | | 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.
* Salvage a little bit of work from a failed patch: simplify and speed upTom Lane2008-10-17
| | | | | | | 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).
* Improve comments about RelOptInfo.reltargetlist.Tom Lane2008-10-17
|
* Improve headeline generation. Now headline can containTeodor Sigaev2008-10-17
| | | | | | several fragments a-la Google. Sushant Sinha <sushant354@gmail.com>
* Fix small bug in headline generation.Teodor Sigaev2008-10-17
| | | | | Patch from Sushant Sinha <sushant354@gmail.com> http://archives.postgresql.org/pgsql-hackers/2008-07/msg00785.php
* During repeated rescan of GiST index it's possible that scan keyTeodor Sigaev2008-10-17
| | | | | | | | | 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.
* Fix a small memory leak in ExecReScanAgg() in the hashed aggregation case.Neil Conway2008-10-16
| | | | | | | 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().
* Reduce chatter from _dosmaperr() when used in FRONTEND code.Tom Lane2008-10-16
| | | | ITAGAKI Takahiro
* Fix SPI_getvalue and SPI_getbinval to range-check the given attribute numberTom Lane2008-10-16
| | | | | | | | | | | | | | 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.
* Make the system-attributes loop in AddNewAttributeTuples depend onTom Lane2008-10-14
| | | | | | 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.
* Add a defense to prevent storing pseudo-type data into index columns.Tom Lane2008-10-14
| | | | | | | 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.)
* Ensure that CLUSTER leaves the toast table and index with consistent names,Alvaro Herrera2008-10-14
| | | | by renaming the new copies after the catalog games.
* Extend the date type to support infinity and -infinity, analogously toTom Lane2008-10-14
| | | | | | | 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.
* Fix EncodeSpecialTimestamp to throw error on unrecognized input, rather thanTom Lane2008-10-14
| | | | returning a failure code that none of its callers bothered to check for.
* Fixed parsing of parameters. Added regression test for this.Michael Meskes2008-10-14
|
* Fix oversight in the relation forks patch: forgot to copy fork number toHeikki Linnakangas2008-10-14
| | | | | fsync requests. This should fix the installcheck failure of the buildfarm member "kudu".
* Add docs and regression test about sorting the output of a recursive query inTom Lane2008-10-14
| | | | | | | | 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 ...
* Eliminate unnecessary array[] decoration in examples of recursive cycleTom Lane2008-10-14
| | | | detection.
* Implement comparison of generic records (composite types), and invent aTom Lane2008-10-13
| | | | | | | | | | | | | 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.
* Update oidjoins test to match CVS HEAD.Tom Lane2008-10-13
|
* Fix bogus comment emitted by make_oidjoins_check, per Greg Stark.Tom Lane2008-10-13
|
* Fix corner case wherein a WorkTableScan node could get initialized before theTom Lane2008-10-13
| | | | | | RecursiveUnion to which it refers. It turns out that we can just postpone the relevant initialization steps until the first exec call for the node, by which time the ancestor node must surely be initialized. Per report from Greg Stark.
* Add missing header.Alvaro Herrera2008-10-11
|
* Fix small query-lifespan memory leak introduced by 8.4 change in index AM APITom Lane2008-10-10
| | | | for bitmap index scans. Per report and test case from Kevin Grittner.
* Fix omission of DiscardStmt in GetCommandLogLevel, per report from HubertTom Lane2008-10-10
| | | | | Depesz Lubaczewski. In HEAD, also move a couple of other cases to make the code ordering match up with ProcessUtility.
* Fixed "create role" parsing to accept optional "with" argument.Michael Meskes2008-10-10
|
* Un-break non-NLS builds.Tom Lane2008-10-09
|
* Fix two flaws in comments I just introduced, pointed out by Tom.Alvaro Herrera2008-10-09
|
* Improve the recently-added code for inlining set-returning functions so thatTom Lane2008-10-09
| | | | | it can handle functions returning setof record. The case was left undone originally, but it turns out to be simple to fix.
* Add initial plpgsql translation (with lots of fuzzies)Alvaro Herrera2008-10-09
|
* Improve translatability of error messages for external modules by tweakingAlvaro Herrera2008-10-09
| | | | | the ereport macro. Included in this commit are enough files for starting plpgsql, plpython, plperl and pltcl translations.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 20:36:34 +0000