- 08 1月, 2011 7 次提交
-
-
由 Bruce Momjian 提交于
which is stored in pg_largeobject_metadata. No backpatch to 9.0 because you can't migrate from 9.0 to 9.0 with the same catversion (because of tablespace conflict), and a pre-9.0 migration to 9.0 has not large object permissions to migrate.
-
由 Bruce Momjian 提交于
Toast tables have identical pg_class.oid and pg_class.relfilenode, but for clarity it is good to preserve the pg_class.oid. Update comments regarding what is preserved, and do some variable/function renaming for clarity.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Add more "internal" arguments so that these pg_proc entries reflect the current preferred API. This is purely a cosmetic change, since GIN doesn't actually consult the pg_proc entry when calling a support function. Accordingly, no catversion bump.
-
由 Tom Lane 提交于
Per my recent proposal(s). Null key datums can now be returned by extractValue and extractQuery functions, and will be stored in the index. Also, placeholder entries are made for indexable items that are NULL or contain no keys according to extractValue. This means that the index is now always complete, having at least one entry for every indexed heap TID, and so we can get rid of the prohibition on full-index scans. A full-index scan is implemented much the same way as partial-match scans were already: we build a bitmap representing all the TIDs found in the index, and then drive the results off that. Also, introduce a concept of a "search mode" that can be requested by extractQuery when the operator requires matching to empty items (this is just as cheap as matching to a single key) or requires a full index scan (which is not so cheap, but it sure beats failing or giving wrong answers). The behavior remains backward compatible for opclasses that don't return any null keys or request a non-default search mode. Using these features, we can now make the GIN index opclass for anyarray behave in a way that matches the actual anyarray operators for &&, <@, @>, and = ... which it failed to do before in assorted corner cases. This commit fixes the core GIN code and ginarrayprocs.c, updates the documentation, and adds some simple regression test cases for the new behaviors using the array operators. The tsearch and contrib GIN opclass support functions still need to be looked over and probably fixed. Another thing I intend to fix separately is that this is pretty inefficient for cases where more than one scan condition needs a full-index search: we'll run duplicate GinScanEntrys, each one of which builds a large bitmap. There is some existing logic to merge duplicate GinScanEntrys but it needs refactoring to make it work for entries belonging to different scan keys. Note that most of gin.h has been split out into a new file gin_private.h, so that gin.h doesn't export anything that's not supposed to be used by GIN opclasses or the rest of the backend. I did quite a bit of other code beautification work as well, mostly fixing comments and choosing more appropriate names for things.
-
由 Robert Haas 提交于
Itagaki Takahiro, edited by me.
-
由 Robert Haas 提交于
Jehan-Guillaume de Rorthais, with some additional wordsmithing by me.
-
- 07 1月, 2011 4 次提交
-
-
由 Itagaki Takahiro 提交于
Itagaki Takahiro and Simon Riggs.
-
由 Bruce Momjian 提交于
functions.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
The previous example didn't make it clear whether array_upper returned the last element or the index of the last element.
-
- 06 1月, 2011 7 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
lo_insert.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
handling. (metadata user ids still an open issue).
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
up pg_dump's calling of pg_upgrade_support functions.
-
- 05 1月, 2011 4 次提交
-
-
由 Magnus Hagander 提交于
This can be overriden by using NOREPLICATION on the CREATE ROLE statement, but by default they will have it, making it backwards compatible and "less surprising" (given that superusers normally override all checks).
-
由 Bruce Momjian 提交于
servers because, like pg_largeobject, it is a system table whose contents are not dumped by pg_dump --schema-only.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 04 1月, 2011 2 次提交
-
-
由 Itagaki Takahiro 提交于
Missing support for VALID UNTIL in CREATE ROLE is also added.
-
由 Robert Haas 提交于
In the previous coding, the parser emitted a List containing a C string, which is no good, because copyObject() can't handle it. Dimitri Fontaine
-
- 03 1月, 2011 5 次提交
-
-
由 Robert Haas 提交于
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
Add the view pg_stat_database_conflicts and a column to pg_stat_database, and the underlying functions to provide the information.
-
由 Magnus Hagander 提交于
Noted by Peter E.
-
由 Magnus Hagander 提交于
Forgot this with previuos commit, line it up so it's easier to submit (readable) patches against the MSVC build system.
-
- 02 1月, 2011 10 次提交
-
-
由 Peter Eisentraut 提交于
Add new function pg_sequence_parameters that returns a sequence's start, minimum, maximum, increment, and cycle values, and use that in the view. (bug #5662; design suggestion by Tom Lane) Also slightly adjust the view's column order and permissions after review of SQL standard.
-
由 Robert Haas 提交于
Noted by Magnus Hagander.
-
由 Robert Haas 提交于
Foreign tables are a core component of SQL/MED. This commit does not provide a working SQL/MED infrastructure, because foreign tables cannot yet be queried. Support for foreign table scans will need to be added in a future patch. However, this patch creates the necessary system catalog structure, syntax support, and support for ancillary operations such as COMMENT and SECURITY LABEL. Shigeru Hanada, heavily revised by Robert Haas
-
由 Robert Haas 提交于
As suggested by Tom Lane, in response to a gripe from Leslie S Satenstein.
-
由 Robert Haas 提交于
Along the way, correct an erroneous comment.
-
由 Peter Eisentraut 提交于
This is analogous to the existing facility that allows casting a row type to a supertable's row type.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
pointers, which simplifies the code. This was not possible in 9.0 because everything was in a single nested struct, but is possible now. Per suggestion from Tom.
-
- 01 1月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
-