aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Add pgmagic header block to store compile-time constants:Bruce Momjian2006-05-30
| | | | | | | | | | | | | | | | | | | | | It now only checks four things: Major version number (7.4 or 8.1 for example) NAMEDATALEN FUNC_MAX_ARGS INDEX_MAX_KEYS The three constants were chosen because: 1. We document them in the config page in the docs 2. We mark them as changable in pg_config_manual.h 3. Changing any of these will break some of the more popular modules: FUNC_MAX_ARGS changes fmgr interface, every module uses this NAMEDATALEN changes syscache interface, every PL as well as tsearch uses this INDEX_MAX_KEYS breaks tsearch and anything using GiST. Martijn van Oosterhout
* Revert patch, needs more work:Bruce Momjian2006-05-30
| | | | | | | | | | | | | | --------------------------------------------------------------------------- Add dynamic record inspection to PL/PgSQL, useful for generic triggers: tval2 := r.(cname); or columns := r.(*); Titus von Boxberg
* Add dynamic record inspection to PL/PgSQL, useful for generic triggers:Bruce Momjian2006-05-30
| | | | | | | | | | tval2 := r.(cname); or columns := r.(*); Titus von Boxberg
* Back out patch, wrong previous commit message.Bruce Momjian2006-05-30
|
* Add regexp_replace() to string functions section.Bruce Momjian2006-05-30
| | | | Joachim Wieland
* Update PL documentation:Bruce Momjian2006-05-30
| | | | | | | | | An article at WebProNews quoted from the PG docs as to the merits of stored procedures. I have added a bit more material on their merits, as well as making a few changes to improve the introductions to PL/Perl and PL/Tcl. Chris Browne
* Update Japanese FAQ.Bruce Momjian2006-05-30
| | | | J.Kuwamura
* Add item:Bruce Momjian2006-05-30
| | | | | | > * Consider GnuTLS if OpenSSL license becomes a problem > > See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php.
* Add:Bruce Momjian2006-05-29
| | | | | > o Allow timezone names in SQL strings, '2006-05-24 21:11 > Americas/New_York'::timestamptz
* Make plperl's $_TD trigger data a global rather than a lexical variable,Andrew Dunstan2006-05-29
| | | | | with a fresh local value for each invocation, to avoid unexpected sharing violations. Per recent -hackers discussion.
* TG_table_name and TG_table_schema for plpgsql, plus docs and regression.Andrew Dunstan2006-05-28
|
* Remove traces of otherwise unused RELKIND_SPECIAL symbol. Leave the psql bitsAlvaro Herrera2006-05-28
| | | | | | in place though, so that it plays nicely with older servers. Per discussion.
* TG_table_name and TG_table_schema for pl/tcl, plus regression test and docs.Andrew Dunstan2006-05-27
|
* Support binary COPY through psql. Also improve detection of write errorsTom Lane2006-05-26
| | | | during COPY OUT. Andreas Pflug, some editorialization by moi.
* Add table_name and table_schema to plpython trigger data, plus docs and ↵Andrew Dunstan2006-05-26
| | | | regression test.
* Add table_name and table_schema to plperl trigger data. relname isAndrew Dunstan2006-05-26
| | | | | | kept but now deprecated. Patch from Adam Sjøgren. Add regression test to show plperl trigger data (Andrew). TBD: apply similar changes to plpgsql, plpython and pltcl.
* Remove pg_attribute detail, add URLBruce Momjian2006-05-24
| | | | | | < pg_attribute.attislocal has to be set to 'false' for ADD, and < pg_attribute.attinhcount adjusted appropriately > See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php.
* * Add support NULL to GiST.Teodor Sigaev2006-05-24
| | | | | | | | * some refactoring and simplify code int gistutil.c and gist.c * now in some cases it can be called used-defined picksplit method for non-first column in index, but here is a place to do more. * small fix of docs related to support NULL.
* Add PQisthreadsafe() to libpq, to allow library applications to queryBruce Momjian2006-05-23
| | | | the thread-safety status of the library.
* Update text:Bruce Momjian2006-05-23
| | | | | > This allows tables to be added/removed from an inheritance > hierarchy. This is particularly useful for table partitioning.
* Add:Bruce Momjian2006-05-23
| | | | | | | | > o Add ALTER TABLE tab ADD/DROP INHERITS parent > > pg_attribute.attislocal has to be set to 'false' for ADD, and > pg_attribute.attinhcount adjusted appropriately >
* Rename in release notes: Mac -> OS/X, Intel to x86:Bruce Momjian2006-05-23
| | | | Fix for OS/X Bonjour on x86 systems (Ashley Clark)
* New wording, "What is the upgrade process for PostgreSQL?"Bruce Momjian2006-05-23
|
* Update heading for upgrades.Bruce Momjian2006-05-23
|
* Add mention that everyone should upgrade to minor releases.Bruce Momjian2006-05-23
|
* Make "trigger" section:Bruce Momjian2006-05-22
| | | | | | | | | | | | | | | | | | | | | > * Referential Integrity > > o Add MATCH PARTIAL referential integrity > o Change foreign key constraint for array -> element to mean element > in array? > o Enforce referential integrity for system tables > > < Referential Integrity < ===================== < < * Add MATCH PARTIAL referential integrity > Triggers > ======== < * Change foreign key constraint for array -> element to mean element < in array? 801d804 < * Enforce referential integrity for system tables
* Update Japanese FAQ.Bruce Momjian2006-05-22
| | | | J.Kuwamura
* Update release notes for upcoming releases.Tom Lane2006-05-21
|
* Modify libpq's string-escaping routines to be aware of encoding considerationsTom Lane2006-05-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and standard_conforming_strings. The encoding changes are needed for proper escaping in multibyte encodings, as per the SQL-injection vulnerabilities noted in CVE-2006-2313 and CVE-2006-2314. Concurrent fixes are being applied to the server to ensure that it rejects queries that may have been corrupted by attempted SQL injection, but this merely guarantees that unpatched clients will fail rather than allow injection. An actual fix requires changing the client-side code. While at it we have also fixed these routines to understand about standard_conforming_strings, so that the upcoming changeover to SQL-spec string syntax can be somewhat transparent to client code. Since the existing API of PQescapeString and PQescapeBytea provides no way to inform them which settings are in use, these functions are now deprecated in favor of new functions PQescapeStringConn and PQescapeByteaConn. The new functions take the PGconn to which the string will be sent as an additional parameter, and look inside the connection structure to determine what to do. So as to provide some functionality for clients using the old functions, libpq stores the latest encoding and standard_conforming_strings values received from the backend in static variables, and the old functions consult these variables. This will work reliably in clients using only one Postgres connection at a time, or even multiple connections if they all use the same encoding and string syntax settings; which should cover many practical scenarios. Clients that use homebrew escaping methods, such as PHP's addslashes() function or even hardwired regexp substitution, will require extra effort to fix :-(. It is strongly recommended that such code be replaced by use of PQescapeStringConn/PQescapeByteaConn if at all feasible.
* Add a new GUC parameter backslash_quote, which determines whether the SQLTom Lane2006-05-21
| | | | | | | | | | | | | | | | | parser will allow "\'" to be used to represent a literal quote mark. The "\'" representation has been deprecated for some time in favor of the SQL-standard representation "''" (two single quote marks), but it has been used often enough that just disallowing it immediately won't do. Hence backslash_quote allows the settings "on", "off", and "safe_encoding", the last meaning to allow "\'" only if client_encoding is a valid server encoding. That is now the default, and the reason is that in encodings such as SJIS that allow 0x5c (ASCII backslash) to be the last byte of a multibyte character, accepting "\'" allows SQL-injection attacks as per CVE-2006-2314 (further details will be published after release). The "on" setting is available for backward compatibility, but it must not be used with clients that are exposed to untrusted input. Thanks to Akio Ishida and Yasuo Ohgaki for identifying this security issue.
* Add last-vacuum/analyze-time columns to the stats collector, both manual andAlvaro Herrera2006-05-19
| | | | | | | | | issued by autovacuum. Add accessor functions to them, and use those in the pg_stat_*_tables system views. Catalog version bumped due to changes in the pgstat views and the pgstat file. Patch from Larry Rosenman, minor improvements by me.
* Stamp 8.1.4, except configure/configure.in.Bruce Momjian2006-05-19
|
* Update for version 8.1.4.Bruce Momjian2006-05-19
|
* Update release notes for 8.1.4.Bruce Momjian2006-05-19
|
* Change <type>string</> to <parameter>string</>.Bruce Momjian2006-05-18
|
* Add:Bruce Momjian2006-05-18
| | | | | | > > * Add a GUC to control whether BEGIN inside a transcation should abort > the transaction.
* Make function param_name/type documentation more consistent.Bruce Momjian2006-05-18
|
* Allow the .pgpass hostname to match the default socket directory, asBruce Momjian2006-05-17
| | | | well as a blank pghost.
* Update pg_dump vesion wording.Bruce Momjian2006-05-13
|
* Mention version portability of pg_dump.Bruce Momjian2006-05-13
|
* Code review for standard_conforming_strings patch. Fix it so it does notTom Lane2006-05-11
| | | | | | | throw warnings for 100%-SQL-standard constructs, clean up some minor infelicities, try to un-break ecpg to the best of my ability. (It's not clear how ecpg is going to find out the setting of standard_conforming_strings, though.) I think pg_dump still needs work, too.
* Clean up code associated with updating pg_class statistics columnsTom Lane2006-05-10
| | | | | | | | | | | (relpages/reltuples). To do this, create formal support in heapam.c for "overwrite" tuple updates (including xlog replay capability) and use that instead of the ad-hoc overwrites we'd been using in VACUUM and CREATE INDEX. Take the responsibility for updating stats during CREATE INDEX out of the individual index AMs, and do it where it belongs, in catalog/index.c. Aside from being more modular, this avoids having to update the same tuple twice in some paths through CREATE INDEX. It's probably not measurably faster, but for sure it's a lot cleaner than before.
* Revert documentation mention of array dimension checking, in next paragraph.Bruce Momjian2006-05-09
|
* Mention array dimmensions are not enforced either.Bruce Momjian2006-05-09
|
* Add description:Bruce Momjian2006-05-06
| | | | | | | | | * %Disallow changing DEFAULT expression of a SERIAL column? > > This should be done only if the existing SERIAL problems cannot be > fixed. >
* Recommend more clearly custom pg_dump format over tar, buy showingBruce Momjian2006-05-06
| | | | custom format examples first.
* Document SSL CRL usage by libpq.Bruce Momjian2006-05-06
|
* Add/ cleanup:Bruce Momjian2006-05-05
| | | | | | | | | | < * %Disallow changing default expression of a SERIAL column? > * %Disallow changing DEFAULT expression of a SERIAL column? 472a473,476 > * Add DEFAULT .. AS OWNER so permission checks are done as the table > owner > > This would be useful for SERIAL nextval() calls and CHECK constraints.
* Rethink the locking mechanisms used for CREATE/DROP/RENAME DATABASE.Tom Lane2006-05-04
| | | | | | | | | | | | | The former approach used ExclusiveLock on pg_database, which being a cluster-wide lock meant only one of these operations could proceed at a time; worse, it also blocked all incoming connections in ReverifyMyDatabase. Now that we have LockSharedObject(), we can use locks of different types applied to databases considered as objects. This allows much more flexible management of the interlocking: two CREATE DATABASEs need not block each other, and need not block connections except to the template database being used. Similarly DROP DATABASE doesn't block unrelated operations. The locking used in flatfiles.c is also much narrower in scope than before. Per recent proposal.
* Clean up API for ambulkdelete/amvacuumcleanup as per today's discussion.Tom Lane2006-05-02
| | | | | | This formulation requires every AM to provide amvacuumcleanup, unlike before, but it's surely a whole lot cleaner. Also, add an 'amstorage' column to pg_am so that we can get rid of hardwired knowledge in DefineOpClass().
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-11 11:08:52 +0000