aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* 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.
* Fix pg_dump support for security labels on columns.Robert Haas2011-01-01
| | | | Along the way, correct an erroneous comment.
* Allow casting a table's row type to the table's supertype if it's a typed tablePeter Eisentraut2011-01-01
| | | | | This is analogous to the existing facility that allows casting a row type to a supertable's row type.
* Add #include <time.h> to pg_ctl.c to fix compiler warning.Bruce Momjian2011-01-01
|
* Stamp copyrights for year 2011.Bruce Momjian2011-01-01
|
* Furter pg_upgrade optimizations to reduce function call argument count.Bruce Momjian2011-01-01
|
* In pg_upgrade, remove use of whichCluster, and just pass old/new clusterBruce Momjian2011-01-01
| | | | | | | 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.
* In pg_upgrade, rename "CLUSTERNAME" to "CLUSTER_NAME".Bruce Momjian2010-12-31
|
* Include the first valid listen address in pg_ctl to improve server startBruce Momjian2010-12-31
| | | | | "wait" detection and add postmaster start time to help determine if the postmaster is actually using the specified data directory.
* Invert and rename flag variable to improve code readability.Tom Lane2010-12-31
| | | | No change in functionality. Per discussion with Robert.
* Move symbols for ExecMergeJoin's state machine into nodeMergejoin.c.Tom Lane2010-12-30
| | | | | There's no reason for these values to be known anywhere else. After doing this, executor/execdefs.h is vestigial and can be removed.
* Support RIGHT and FULL OUTER JOIN in hash joins.Tom Lane2010-12-30
| | | | | | | | | | | | | | | | | | | | | | This is advantageous first because it allows us to hash the smaller table regardless of the outer-join type, and second because hash join can be more flexible than merge join in dealing with arbitrary join quals in a FULL join. For merge join all the join quals have to be mergejoinable, but hash join will work so long as there's at least one hashjoinable qual --- the others can be any condition. (This is true essentially because we don't keep per-inner-tuple match flags in merge join, while hash join can do so.) To do this, we need a has-it-been-matched flag for each tuple in the hashtable, not just one for the current outer tuple. The key idea that makes this practical is that we can store the match flag in the tuple's infomask, since there are lots of bits there that are of no interest for a MinimalTuple. So we aren't increasing the size of the hashtable at all for the feature. To write this without turning the hash code into even more of a pile of spaghetti than it already was, I rewrote ExecHashJoin in a state-machine style, similar to ExecMergeJoin. Other than that decision, it was pretty straightforward.
* Remove tabs in SGMLPeter Eisentraut2010-12-30
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 12:50:43 +0000