aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Create core infrastructure for KNNGIST.Tom Lane2010-12-02
| | | | | | | | | | | | | | | | | | | This is a heavily revised version of builtin_knngist_core-0.9. The ordering operators are no longer mixed in with actual quals, which would have confused not only humans but significant parts of the planner. Instead, ordering operators are carried separately throughout planning and execution. Since the API for ambeginscan and amrescan functions had to be changed anyway, this commit takes the opportunity to rationalize that a bit. RelationGetIndexScan no longer forces a premature index_rescan call; instead, callers of index_beginscan must call index_rescan too. Aside from making the AM-side initialization logic a bit less peculiar, this has the advantage that we do not make a useless extra am_rescan call when there are runtime key values. AMs formerly could not assume that the key values passed to amrescan were actually valid; now they can. Teodor Sigaev and Tom Lane
* Be consistent about writing "[, ...]" instead "[,...]" in the docs.Heikki Linnakangas2010-11-29
| | | | Christoph Berg.
* Point out in default_tablespace's description that CREATE DATABASE ignores it.Tom Lane2010-11-27
| | | | Per gripe from Andreas Scherbaum.
* New contrib module, auth_delay.Robert Haas2010-11-27
| | | | KaiGai Kohei, with a few changes by me.
* A bit more wordsmithing on the PQping documentation.Tom Lane2010-11-27
|
* Rewrite PQping to be more like what we agreed to last week.Tom Lane2010-11-27
| | | | | | | | | | | | | | | | | | | | | | | Basically, we want to distinguish all cases where the connection was not made from those where it was. A convenient proxy for this is to see if we got a message with a SQLSTATE code back from the postmaster. This presumes that the postmaster will always send us a SQLSTATE in a failure message, which is true for 7.4 and later postmasters in every case except fork failure. (We could possibly complicate the postmaster code to do something about that, but it seems not worth the trouble, especially since pg_ctl's response for that case should be to keep waiting anyway.) If we did get a SQLSTATE from the postmaster, there are basically only two cases, as per last week's discussion: ERRCODE_CANNOT_CONNECT_NOW and everything else. Any other error code implies that the postmaster is in principle willing to accept connections, it just didn't like or couldn't handle this particular request. We want to make a special case for ERRCODE_CANNOT_CONNECT_NOW so that "pg_ctl start -w" knows it should keep waiting. In passing, pick names for the enum constants that are a tad less likely to present collision hazards in future.
* Add more ALTER <object> .. SET SCHEMA commands.Robert Haas2010-11-26
| | | | | | | | This adds support for changing the schema of a conversion, operator, operator class, operator family, text search configuration, text search dictionary, text search parser, or text search template. Dimitri Fontaine, with assorted corrections and other kibitzing.
* Add PQping and PQpingParams to libpq to allow detection of the server'sBruce Momjian2010-11-25
| | | | | | | | | status, including a status where the server is running but refuses a postgres connection. Have pg_ctl use this new function. This fixes the case where pg_ctl reports that the server is not running (cannot connect) but in fact it is running.
* Document that a CHECKPOINT before taking a file system snapshot canBruce Momjian2010-11-24
| | | | reduce recovery time.
* When reporting the server as not responding, if the hostname wasBruce Momjian2010-11-24
| | | | | | | | | supplied, also print the IP address. This allows IPv4 and IPv6 failures to be distinguished. Also useful when a hostname resolves to multiple IP addresses. Also, remove use of inet_ntoa() and use our own inet_net_ntop() in all places, including in libpq, because it is thread-safe.
* Create the system catalog infrastructure needed for KNNGIST.Tom Lane2010-11-24
| | | | | | | | | | | | | | | | This commit adds columns amoppurpose and amopsortfamily to pg_amop, and column amcanorderbyop to pg_am. For the moment all the entries in amcanorderbyop are "false", since the underlying support isn't there yet. Also, extend the CREATE OPERATOR CLASS/ALTER OPERATOR FAMILY commands with [ FOR SEARCH | FOR ORDER BY sort_operator_family ] clauses to allow the new columns of pg_amop to be populated, and create pg_dump support for dumping that information. I also added some documentation, although it's perhaps a bit premature given that the feature doesn't do anything useful yet. Teodor Sigaev, Robert Haas, Tom Lane
* Add index entries for more functionsPeter Eisentraut2010-11-24
| | | | | | | | | Also, move index entries into the tables, closer to the function description, for easier editing in the future. Resort some tables to be more alphabetical. Remove the entries for count, max, min, and sum in the tutorial area, because that was felt to be confusing. Thom Brown
* Propagate ALTER TYPE operations to typed tablesPeter Eisentraut2010-11-23
| | | | | This adds RESTRICT/CASCADE flags to ALTER TYPE ... ADD/DROP/ALTER/ RENAME ATTRIBUTE to control whether to alter typed tables as well.
* Remove useless whitespace at end of linesPeter Eisentraut2010-11-23
|
* Add new SQL function, format(text).Robert Haas2010-11-20
| | | | | | | | | | | Currently, three conversion format specifiers are supported: %s for a string, %L for an SQL literal, and %I for an SQL identifier. The latter two are deliberately designed not to overlap with what sprintf() already supports, in case we want to add more of sprintf()'s functionality here later. Patch by Pavel Stehule, heavily revised by me. Reviewed by Jeff Janes and, in earlier versions, by Itagaki Takahiro and Tom Lane.
* Add pg_describe_object functionAlvaro Herrera2010-11-18
| | | | | This function is useful to obtain textual descriptions of objects as stored in pg_depend.
* Minor corrections to dummy_seclabel documentation.Robert Haas2010-11-18
| | | | Problems noted by Thom Brown.
* Document the dummy_seclabel contrib module.Robert Haas2010-11-17
| | | | KaiGai Kohei, with editing and markup fixes by me.
* Make TRUNCATE ... RESTART IDENTITY restart sequences transactionally.Tom Lane2010-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the previous coding, we simply issued ALTER SEQUENCE RESTART commands, which do not roll back on error. This meant that an error between truncating and committing left the sequences out of sync with the table contents, with potentially bad consequences as were noted in a Warning on the TRUNCATE man page. To fix, create a new storage file (relfilenode) for a sequence that is to be reset due to RESTART IDENTITY. If the transaction aborts, we'll automatically revert to the old storage file. This acts just like a rewriting ALTER TABLE operation. A penalty is that we have to take exclusive lock on the sequence, but since we've already got exclusive lock on its owning table, that seems unlikely to be much of a problem. The interaction of this with usual nontransactional behaviors of sequence operations is a bit weird, but it's hard to see what would be completely consistent. Our choice is to discard cached-but-unissued sequence values both when the RESTART is executed, and at rollback if any; but to not touch the currval() state either time. In passing, move the sequence reset operations to happen before not after any AFTER TRUNCATE triggers are fired. The previous ordering was not logically sensible, but was forced by the need to minimize inconsistency if the triggers caused an error. Transactional rollback is a much better solution to that. Patch by Steve Singer, rather heavily adjusted by me.
* Require VALUE keyword when extending an enum type. Based on a patch from ↵Andrew Dunstan2010-11-16
| | | | Alvaro Herrera.
* Add new buffers_backend_fsync field to pg_stat_bgwriter.Robert Haas2010-11-15
| | | | | | | | | | | | This new field counts the number of times that a backend which writes a buffer out to the OS must also fsync() it. This happens when the bgwriter fsync request queue is full, and is generally detrimental to performance, so it's good to know when it's happening. Along the way, log a new message at level DEBUG1 whenever we fail to hand off an fsync, so that the problem can also be seen in examination of log files (if the logging level is cranked up high enough). Greg Smith, with minor tweaks by me.
* Improved parallel make supportPeter Eisentraut2010-11-12
| | | | | | | | Replace for loops in makefiles with proper dependencies. Parallel make can now span across directories. Also, make -k and make -q work properly. GNU make 3.80 or newer is now required.
* docs -> documentationPeter Eisentraut2010-11-12
|
* Mention that pg_upgrade requires compatible 32/64-bit binaries.Bruce Momjian2010-11-10
|
* Add monitoring function pg_last_xact_replay_timestamp.Robert Haas2010-11-09
| | | | Fujii Masao, with a little wordsmithing by me.
* Merge docs for CREATE CONSTRAINT TRIGGER and CREATE TRIGGERAlvaro Herrera2010-11-09
|
* Improve pg_ctl's man page.Tom Lane2010-11-09
| | | | | | Explicitly document that the -o options of pg_ctl init mode are meant for initdb, not postgres (Euler Taveira de Oliveira). Assorted other copy-editing (Tom).
* plpython has plpy.Error instead of plpy.ERRORAlvaro Herrera2010-11-09
| | | | Author: Marti Raudsepp <marti@juffo.org>
* Prevent invoking I/O conversion casts via functional/attribute notation.Tom Lane2010-11-07
| | | | | | | | | | | | | | | PG 8.4 added a built-in feature for casting pretty much any data type to string types (text, varchar, etc). We allowed this to work in any of the historically-allowed syntaxes: CAST(x AS text), x::text, text(x), or x.text. However, multiple complaints have shown that it's too easy to invoke such casts unintentionally in the latter two styles, particularly field selection. To cure the problem with the narrowest possible change of behavior, disallow use of I/O conversion casts from composite types to string types via functional/attribute syntax. The new functionality is still available via cast syntax. In passing, document the equivalence of functional and attribute syntax in a more visible place.
* Implement an "S" option for psql's \dn command.Tom Lane2010-11-06
| | | | | | | \dn without "S" now hides all pg_XXX schemas as well as information_schema. Thus, in a bare database you'll only see "public". ("public" is considered a user schema, not a system schema, mainly because it's droppable.) Per discussion back in late September.
* Allow moddatetime's target column to be of type timestamptz.Tom Lane2010-11-04
| | | | Dirk Heinrichs
* Change version number in release notes to 9.1alpha2Peter Eisentraut2010-10-30
|
* Last-minute updates to 9.1alpha2 release notesPeter Eisentraut2010-10-30
|
* Release notes for 9.1alpha2Peter Eisentraut2010-10-28
|
* Remove obsolete release-alpha.sgmlPeter Eisentraut2010-10-28
| | | | | This was only used while the final release notes for 9.0 were being prepared. The alpha release notes are now in release-9.1.sgml.
* Remove tabs from SGMLPeter Eisentraut2010-10-28
|
* Revert "Correct WAL space calculation formula in docs."Robert Haas2010-10-27
| | | | | | | | This reverts commit 915116bc62db2aaec7001bde6610128f4cbd29f9. Per discussion, the previous formula was in fact correct. http://archives.postgresql.org/pgsql-docs/2010-10/msg00038.php
* Reorganize OS-specific details about write caching into a list.Robert Haas2010-10-27
| | | | Along the way, clarify that sdparm can be used on Linux as well as FreeBSD.
* Note that effective_io_concurrency only affects bitmap heap scans.Robert Haas2010-10-26
| | | | Josh Kupershmidt
* Note explicitly that hash indexes are also not replicated because they're notHeikki Linnakangas2010-10-26
| | | | | | WAL-logged. Make the notice about the lack of WAL-logging more visible by making it a <caution>. Also remove the false statement from hot standby caveats section that hash indexes are not used during hot standby.
* Allow new values to be added to an existing enum type.Tom Lane2010-10-24
| | | | | | | After much expenditure of effort, we've got this to the point where the performance penalty is pretty minimal in typical cases. Andrew Dunstan, reviewed by Brendan Jurd, Dean Rasheed, and Tom Lane
* Support suffix matching of host names in pg_hba.confPeter Eisentraut2010-10-24
| | | | | A name starting with a dot can be used to match a suffix of the actual host name (e.g., .example.com matches foo.example.com).
* Add semicolon, missed in previous patch. And update the keyword list inHeikki Linnakangas2010-10-22
| | | | the docs to reflect that OFF is now unreserved. Spotted by Tom Lane.
* Mention limited usefulness of .pgpass database field.Bruce Momjian2010-10-21
|
* Improve handling of domains over arrays.Tom Lane2010-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | This patch eliminates various bizarre behaviors caused by sloppy thinking about the difference between a domain type and its underlying array type. In particular, the operation of updating one element of such an array has to be considered as yielding a value of the underlying array type, *not* a value of the domain, because there's no assurance that the domain's CHECK constraints are still satisfied. If we're intending to store the result back into a domain column, we have to re-cast to the domain type so that constraints are re-checked. For similar reasons, such a domain can't be blindly matched to an ANYARRAY polymorphic parameter, because the polymorphic function is likely to apply array-ish operations that could invalidate the domain constraints. For the moment, we just forbid such matching. We might later wish to insert an automatic downcast to the underlying array type, but such a change should also change matching of domains to ANYELEMENT for consistency. To ensure that all such logic is rechecked, this patch removes the original hack of setting a domain's pg_type.typelem field to match its base type; the typelem will always be zero instead. In those places where it's really okay to look through the domain type with no other logic changes, use the newly added get_base_element_type function in place of get_element_type. catversion bumped due to change in pg_type contents. Per bug #5717 from Richard Huxton and subsequent discussion.
* Add some caveats to the contrib/isn docs.Robert Haas2010-10-19
|
* Update storage.sgml to describe the 9.0 tablespace directory layout.Tom Lane2010-10-19
|
* Add mention of using tools/fsync to test fsync methods. RestructureBruce Momjian2010-10-19
| | | | recent wal_sync_method doc paragraph to be clearer.
* Add levenshtein_less_equal, optimized version for small distances.Robert Haas2010-10-19
| | | | Alexander Korotkov, heavily revised by me.
* Support key word 'all' in host column of pg_hba.confPeter Eisentraut2010-10-18
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-08 02:54:39 +0000