summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Tweak the behavior of log_duration as proposed by Guillaume Smet: ratherTom Lane2006-09-081-15/+14
| | | | | | | than being equivalent to setting log_min_duration_statement to zero, this option now forces logging of all query durations, but doesn't force logging of query text. Also, add duration logging coverage for fastpath function calls.
* Clean up logging for extended-query-protocol operations, as per my recentTom Lane2006-09-071-32/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | proposal. Parameter logging works even for binary-format parameters, and logging overhead is avoided when disabled. log_statement = all output for the src/test/examples/testlibpq3.c example now looks like LOG: statement: execute <unnamed>: SELECT * FROM test1 WHERE t = $1 DETAIL: parameters: $1 = 'joe''s place' LOG: statement: execute <unnamed>: SELECT * FROM test1 WHERE i = $1::int4 DETAIL: parameters: $1 = '2' and log_min_duration_statement = 0 results in LOG: duration: 2.431 ms parse <unnamed>: SELECT * FROM test1 WHERE t = $1 LOG: duration: 2.335 ms bind <unnamed> to <unnamed>: SELECT * FROM test1 WHERE t = $1 DETAIL: parameters: $1 = 'joe''s place' LOG: duration: 0.394 ms execute <unnamed>: SELECT * FROM test1 WHERE t = $1 DETAIL: parameters: $1 = 'joe''s place' LOG: duration: 1.251 ms parse <unnamed>: SELECT * FROM test1 WHERE i = $1::int4 LOG: duration: 0.566 ms bind <unnamed> to <unnamed>: SELECT * FROM test1 WHERE i = $1::int4 DETAIL: parameters: $1 = '2' LOG: duration: 0.173 ms execute <unnamed>: SELECT * FROM test1 WHERE i = $1::int4 DETAIL: parameters: $1 = '2' (This example demonstrates the folly of ignoring parse/bind steps for duration logging purposes, BTW.) Along the way, create a less ad-hoc mechanism for determining which commands are logged by log_statement = mod and log_statement = ddl. The former coding was actually missing quite a few things that look like ddl to me, and it did not handle EXECUTE or extended query protocol correctly at all. This commit does not do anything about the question of whether log_duration should be removed or made less redundant with log_min_duration_statement.
* HTLM cleanup.Bruce Momjian2006-09-072-12/+13
|
* Update Emacs/vim editor info.Bruce Momjian2006-09-072-40/+7
|
* Update emacs info for FAQ_DEV.Bruce Momjian2006-09-072-74/+15
| | | | Andrew Dunstan
* Add XML documentation.Bruce Momjian2006-09-071-1/+149
|
* Update tools directory name.Bruce Momjian2006-09-062-4/+4
|
* Change processing of extended-Query mode so that an unnamed statementTom Lane2006-09-061-18/+10
| | | | | | | | that has parameters is always planned afresh for each Bind command, treating the parameter values as constants in the planner. This removes the performance penalty formerly often paid for using out-of-line parameters --- with this definition, the planner can do constant folding, LIKE optimization, etc. After a suggestion by Andrew@supernews.
* Get rid of the separate RULE privilege for tables: now only a table's ownerTom Lane2006-09-057-35/+23
| | | | | | | | | | | | | can create or modify rules for the table. Do setRuleCheckAsUser() while loading rules into the relcache, rather than when defining a rule. This ensures that permission checks for tables referenced in a rule are done with respect to the current owner of the rule's table, whereas formerly ALTER TABLE OWNER would fail to update the permission checking for associated rules. Removal of separate RULE privilege is needed to prevent various scenarios in which a grantee of RULE privilege could effectively have any privilege of the table owner. For backwards compatibility, GRANT/REVOKE RULE is still accepted, but it doesn't do anything. Per discussion here: http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php
* Remove GIN documentationBruce Momjian2006-09-053-173/+2
| | | | Christopher Kings-Lynne
* Update Japanese FAQ.Bruce Momjian2006-09-052-32/+30
| | | | Jun Kuwamura
* Update setseed() documentation.Bruce Momjian2006-09-041-2/+2
|
* Update LDAP installation wording.Bruce Momjian2006-09-041-3/+4
| | | | Albe Laurenz
* Add GIN documentation.Bruce Momjian2006-09-043-2/+173
| | | | Christopher Kings-Lynne
* Mention paremeterized queries do not work with partial indexes.Bruce Momjian2006-09-041-2/+7
| | | | Simon Riggs
* Code review for UPDATE SET (columnlist) patch. Make it handle as muchTom Lane2006-09-031-7/+24
| | | | | | of the syntax as this fundamentally dead-end approach can, in particular combinations of single and multi column assignments. Improve rather inadequate documentation and provide some regression tests.
* Remove duplicated index entry.Tom Lane2006-09-031-4/+2
|
* Fix broken markup.Tom Lane2006-09-031-1/+3
|
* Fix non-improvement of description of archive_timeout. archive_commandTom Lane2006-09-031-3/+3
| | | | | is only invoked on completed WAL segments, period --- there's no 'by default' about it.
* Remove:Bruce Momjian2006-09-032-5/+3
| | | | < * Change LIMIT/OFFSET and FETCH/MOVE to use int8
* Reverted:Bruce Momjian2006-09-032-4/+4
| | | | | < * -Change LIMIT/OFFSET and FETCH/MOVE to use int8 > * Change LIMIT/OFFSET and FETCH/MOVE to use int8
* Update predicate locking text.Bruce Momjian2006-09-031-3/+3
|
* Add:Bruce Momjian2006-09-022-2/+17
| | | | | | | | | | | > * Simplify ability to create partitioned tables > > This would allow creation of partitioned tables without requiring > creation of rules for INSERT/UPDATE/DELETE, and constraints for > rapid partition selection. Options could include range and hash > partition selection. > > * Allow auto-selection of partitioned tables for min/max() operations
* Make autovacuum behavior more agressive, per discussion on hackers listBruce Momjian2006-09-021-5/+5
| | | | | | | --- was part of autovacuum default 'on' patch that was reverted, but we want this part. Peter Eisentraut
* Change "superuser_reserved_connections" default to 3, because ofBruce Momjian2006-09-021-2/+2
| | | | possible autovacuum use.
* Add URL for autovacuum default:Bruce Momjian2006-09-022-2/+6
| | | | | > > http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php
* Wording improvements for archive_timeout.Bruce Momjian2006-09-021-4/+4
|
* Add UPDATE tab SET ROW (col, ...) = (val, ...) for updatingBruce Momjian2006-09-021-2/+7
| | | | | | multiple columns Susanne Ebrecht
* Update:Bruce Momjian2006-09-022-39/+37
| | | | | | | | | | | < Last updated: Sat Sep 2 08:31:04 EDT 2006 > Last updated: Sat Sep 2 16:31:46 EDT 2006 < o Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple < columns > o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating > multiple columns > o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) < A subselect can also be used as the value source.
* Apply a simple solution to the problem of making INSERT/UPDATE/DELETETom Lane2006-09-022-20/+60
| | | | | | | | | | | | | | | RETURNING play nice with views/rules. To wit, have the rule rewriter rewrite any RETURNING clause found in a rule to produce what the rule's triggering query asked for in its RETURNING clause, in particular drop the RETURNING clause if no RETURNING in the triggering query. This leaves the responsibility for knowing how to produce the view's output columns on the rule author, without requiring any fundamental changes in rule semantics such as adding new rule event types would do. The initial implementation constrains things to ensure that there is exactly one, unconditionally invoked RETURNING clause among the rules for an event --- later we might be able to relax that, but for a post feature freeze fix it seems better to minimize how much invention we do. Per gripe from Jaime Casanova.
* Add new variable "server_version_num", which is almost the same asBruce Momjian2006-09-021-1/+14
| | | | | | | | "server_version" but uses the handy PG_VERSION_NUM which allows apps to do things like if ($version >= 80200) without having to parse apart the value of server_version themselves. Greg Sabino Mullane greg@turnstep.com
* Update wording:Bruce Momjian2006-09-022-4/+4
| | | | | < o -Allow PL/python to composite types and result sets > o -Allow PL/python to return composite types and result sets
* Allow PL/python to return composite types and result setsBruce Momjian2006-09-021-17/+287
| | | | Sven Suursoho
* Done:Bruce Momjian2006-09-022-9/+4
| | | | o -Allow PL/python to composite types and result sets
* Done:Bruce Momjian2006-08-312-41/+34
| | | | | | | | | | | < Last updated: Tue Aug 29 12:21:52 EDT 2006 > Last updated: Wed Aug 30 20:34:28 EDT 2006 < o Allow COPY (SELECT ...) TO 'filename' < < COPY should also be able to output views using COPY (SELECT < * FROM view) TO 'filename' internally. < http://archives.postgresql.org/pgsql-patches/2005-09/msg00148.php > o -Allow COPY (SELECT ...) TO 'filename'
* Extend COPY to support COPY (SELECT ...) TO ...Tom Lane2006-08-302-22/+27
| | | | Bernd Helmle
* Create a FETCH_COUNT parameter that causes psql to execute SELECT-likeTom Lane2006-08-291-1/+28
| | | | | | | | queries via a cursor, fetching a limited number of rows at a time and therefore not risking exhausting memory. A disadvantage of the scheme is that 'aligned' output mode will align each group of rows independently leading to odd-looking output, but all the other output formats work reasonably well. Chris Mair, with some additional hacking by moi.
* Add autovacuum item:Bruce Momjian2006-08-292-2/+4
| | | | > o Turn on by default
* Revert change to turn autovacuum on by default.Peter Eisentraut2006-08-292-14/+11
|
* Now bind displays prepare as detail, and execute displays prepare andBruce Momjian2006-08-291-2/+2
| | | | | | | | | | optionally bind. I re-added the "statement:" label so people will understand why the line is being printed (it is log_*statement behavior). Use single quotes for bind values, instead of double quotes, and double literal single quotes in bind values (and document that). I also made use of the DETAIL line to have much cleaner output.
* Add URL:Bruce Momjian2006-08-282-2/+5
| | | | | > http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html >
* Move to referential integrity section:Bruce Momjian2006-08-282-15/+15
| | | | | | | | | | | | | | | | | > o Allow DEFERRABLE and end-of-statement UNIQUE constraints? > > This would allow UPDATE tab SET col = col + 1 to work if col has > a unique index. Currently, uniqueness checks are done while the > command is being executed, rather than at the end of the statement > or transaction. > < < * Allow DEFERRABLE and end-of-statement UNIQUE constraints? < < This would allow UPDATE tab SET col = col + 1 to work if col has < a unique index. Currently, uniqueness checks are done while the < command is being executed, rather than at the end of the statement < or transaction.
* Update:Bruce Momjian2006-08-282-4/+15
| | | | | | | | | | | < * Allow DEFERRABLE UNIQUE constraints? > * Allow DEFERRABLE and end-of-statement UNIQUE constraints? > > This would allow UPDATE tab SET col = col + 1 to work if col has > a unique index. Currently, uniqueness checks are done while the > command is being executed, rather than at the end of the statement > or transaction. >
* Turn autovacuum on by default. (stats_row_level is also on by default.)Peter Eisentraut2006-08-282-11/+14
| | | | Threshold and scale factor are cut in half for more aggressive behavior.
* Add new return codes SPI_OK_INSERT_RETURNING etc to the SPI API.Tom Lane2006-08-271-14/+44
| | | | | | | Fix all the standard PLs to be able to return tuples from FOO_RETURNING statements as well as utility statements that return tuples. Also, fix oversight that SPI_processed wasn't set for a utility statement returning tuples. Per recent discussion.
* Add blank line.>Bruce Momjian2006-08-252-2/+3
|
* Add:Bruce Momjian2006-08-252-3/+4
| | | | | < > * Implement SQL:2003 window functions
* Add the ability to create indexes 'concurrently', that is, withoutTom Lane2006-08-256-11/+155
| | | | | blocking concurrent writes to the table. Greg Stark, with a little help from Tom Lane.
* Add:Bruce Momjian2006-08-242-2/+4
| | | | > * Allow inlining of set-returning functions
* Add "AS" item:Bruce Momjian2006-08-232-6/+17
| | | | | | | | | | | | | < * All backends running as threads in a single process (not want) > * All backends running as threads in a single process (not wanted) < * Optimizer hints (not want) > * Optimizer hints (not wanted) > > * Allow AS in "SELECT col AS label" to be optional (not wanted) > > Because we support postfix operators, it isn't possible to make AS > optional and continue to use bison. > http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
View Lorry Controller Status