aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* There is no need to have to identical functions in ecpg thus removing one of ↵Michael Meskes2011-01-09
| | | | them.
* Fix assorted corner-case bugs in contrib/intarray.Tom Lane2011-01-09
| | | | | | | | | | | | | | | | | | | The array containment operators now behave per mathematical expectation for empty arrays (ie, an empty array is contained in anything). Both these operators and the query_int operators now work as expected in GiST and GIN index searches, rather than having corner cases where the index searches gave different answers. Also, fix unexpected failures where the operators would claim that an array contained nulls, when in fact there was no longer any null present (similar to bug #5784). The restriction to not have nulls is still there, as removing it would take a lot of added code complexity and probably slow things down significantly. Also, remove the arbitrary restriction to 1-D arrays; unlike the other restriction, this was buying us nothing performance-wise. Assorted cosmetic improvements and marginal performance improvements, too.
* Add array_contains_nulls() function in arrayfuncs.c.Tom Lane2011-01-08
| | | | | | This will support fixing contrib/intarray (and probably other places) so that they don't have to fail on arrays that contain a null bitmap but no live null entries.
* Fix up gincostestimate for new extractQuery API.Tom Lane2011-01-08
| | | | | | | | The only reason this wasn't crashing while testing the core anyarray operators was that it was disabled for those cases because of passing the wrong type information to get_opfamily_proc :-(. So fix that too, and make it insist on finding the support proc --- in hindsight, silently doing nothing is not as sane a coping mechanism as all that.
* In ecpg's parser removed a fixed length limit for constants defining an ↵Michael Meskes2011-01-08
| | | | array dimension.
* Remove pg_am.amindexnulls.Tom Lane2011-01-08
| | | | | | | | | The only use we have had for amindexnulls is in determining whether an index is safe to cluster on; but since the addition of the amclusterable flag, that usage is pretty redundant. In passing, clean up assorted sloppiness from the last patch that touched pg_am.h: Natts_pg_am was wrong, and ambuildempty was not documented.
* Refactor GIN's handling of duplicate search entries.Tom Lane2011-01-08
| | | | | | | | The original coding could combine duplicate entries only when they originated from the same qual condition. In particular it could not combine cases where multiple qual conditions all give rise to full-index scan requests, which is an expensive case well worth optimizing. Refactor so that duplicates are recognized across all the quals.
* In pg_upgrade, remove functions that did sequential array scans lookingBruce Momjian2011-01-08
| | | | | | up relations, but rather order old/new relations and use the same array index value for both. This should speed up pg_upgrade for databases with many relations.
* In pg_upgrade, clarify use of install_db_support_functions().Bruce Momjian2011-01-08
|
* In pg_upgrade, remove unnecessary separate handling of toast tables nowBruce Momjian2011-01-08
| | | | | that we restore by oid; they can be handled like regular tables when creating the file mapping structure.
* Remove bogus claims regarding createuser defaults.Robert Haas2011-01-08
| | | | Josh Kupershmidt
* Update GIN support function definitions for contrib/intarray.Tom Lane2011-01-07
| | | | | The underlying C code still needs work, but this at least gets its current regression test passing again.
* Document why pg_upgrade preserves pg_auth.oid (because they are storedBruce Momjian2011-01-07
| | | | in pg_largeobject_metadata).
* More pg_upgrade relfilenode C comments added.Bruce Momjian2011-01-07
|
* Simplify pg_upgrade C comment about what is preserved.Bruce Momjian2011-01-07
|
* In pg_upgrade, track only one copy of namespace/relname in FileNameMapBruce Momjian2011-01-07
| | | | because the old and new values are identical.
* Fix C indenting in pg_upgrade function.Bruce Momjian2011-01-07
|
* Fix pg_upgrade of large object permissions by preserving pg_auth.oid,Bruce Momjian2011-01-07
| | | | | | | | 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.
* Force pg_upgrade's to preserve pg_class.oid, not pg_class.relfilenode.Bruce Momjian2011-01-07
| | | | | | | | 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.
* Ooops, forgot to fix contrib/tsearch2's references to GIN support funcs.Tom Lane2011-01-07
|
* Fix the built-in GIN support procedure declarations in pg_proc.h.Tom Lane2011-01-07
| | | | | | | 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.
* Fix GIN to support null keys, empty and null items, and full index scans.Tom Lane2011-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Document pg_stat_replication, bump catversion since that was overlooked.Robert Haas2011-01-07
| | | | Itagaki Takahiro, edited by me.
* Improve recovery.conf.sample comments.Robert Haas2011-01-07
| | | | Jehan-Guillaume de Rorthais, with some additional wordsmithing by me.
* New system view pg_stat_replication displays activity of wal sender processes.Itagaki Takahiro2011-01-07
| | | | Itagaki Takahiro and Simon Riggs.
* Improve C comments about backend variables set by pg_upgrade_supportBruce Momjian2011-01-06
| | | | functions.
* Improve markup of unnest examplePeter Eisentraut2011-01-07
|
* Improve array_upper examplePeter Eisentraut2011-01-07
| | | | | The previous example didn't make it clear whether array_upper returned the last element or the index of the last element.
* Update sequence_1.out for recent changes in sequence regression test.Tom Lane2011-01-06
|
* Update documentation to say that \lo_import sets :LASTOID, notBruce Momjian2011-01-05
| | | | lo_insert.
* Rename pg_upgrade variables, for clarity.Bruce Momjian2011-01-05
|
* Update pg_upgrade C comments.Bruce Momjian2011-01-05
|
* Fix for recent pg_upgrade commit to fix large objects relfilenodeBruce Momjian2011-01-05
| | | | handling. (metadata user ids still an open issue).
* In pg_upgrade, adjust transfer_relfile()'s parameters to be more logical.Bruce Momjian2011-01-05
|
* Clarify pg_upgrade's creation of the map file structure. Also cleanBruce Momjian2011-01-05
| | | | up pg_dump's calling of pg_upgrade_support functions.
* Give superusers REPLIACTION permission by defaultMagnus Hagander2011-01-05
| | | | | | | 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).
* In pg_upgrade, copy pg_largeobject_metadata and its index for 9.0+Bruce Momjian2011-01-04
| | | | | servers because, like pg_largeobject, it is a system table whose contents are not dumped by pg_dump --schema-only.
* In pg_upgrade, fix backward logging display of link operations.Bruce Momjian2011-01-04
|
* Simplify functions and parameters used by pg_upgrade.Bruce Momjian2011-01-04
|
* Improve psql tab completion for CREATE/ALTER ROLE [NO]REPLICATION.Itagaki Takahiro2011-01-04
| | | | Missing support for VALID UNTIL in CREATE ROLE is also added.
* Fix crash in ALTER OPERATOR CLASS/FAMILY .. SET SCHEMA.Robert Haas2011-01-03
| | | | | | | 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
* Update comments in RecordTransactionCommit() to mention unlogged tables.Robert Haas2011-01-03
|
* Bump catversion, forgot in previous commit.Magnus Hagander2011-01-03
|
* Add views and functions to monitor hot standby query conflictsMagnus Hagander2011-01-03
| | | | | Add the view pg_stat_database_conflicts and a column to pg_stat_database, and the underlying functions to provide the information.
* Add missing part of replication role docsMagnus Hagander2011-01-03
| | | | Noted by Peter E.
* perltidy run on the MSVC build systemMagnus Hagander2011-01-03
| | | | | Forgot this with previuos commit, line it up so it's easier to submit (readable) patches against the MSVC build system.
* Implement remaining fields of information_schema.sequences viewPeter Eisentraut2011-01-02
| | | | | | | | | 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.
* Fix typo.Robert Haas2011-01-02
| | | | Noted by Magnus Hagander.
* Basic foreign table support.Robert Haas2011-01-01
| | | | | | | | | | | 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
* Minor wordsmithing.Robert Haas2011-01-01
| | | | As suggested by Tom Lane, in response to a gripe from Leslie S Satenstein.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 18:31:51 +0000