- 16 9月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Includes sample standby script. Simon Riggs
-
由 Bruce Momjian 提交于
Simon Riggs
-
- 15 9月, 2006 4 次提交
-
-
由 Tom Lane 提交于
a schema is our own temp schema or another backend's temp schema, and use these in place of some former kluges in information_schema. Per my proposal of yesterday.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
UTF8 escapes.
-
- 14 9月, 2006 3 次提交
-
-
由 Teodor Sigaev 提交于
-
由 Teodor Sigaev 提交于
Thanks to Christopher Kings-Lynne <chris.kingslynne@gmail.com> for initial version and Jeff Davis <pgsql@j-davis.com> for inspection
-
由 Tom Lane 提交于
CONCURRENTLY. Greg Stark, some further tweaks by me.
-
- 11 9月, 2006 3 次提交
- 10 9月, 2006 2 次提交
-
-
由 Tom Lane 提交于
agreed these symbols are less easily confused. I made new pg_operator entries (with new OIDs) for the old names, so as to provide backward compatibility while making it pretty easy to remove the old names in some future release cycle. This commit only touches the core datatypes, contrib will be fixed separately.
-
由 Tom Lane 提交于
-
- 08 9月, 2006 2 次提交
-
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
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.
-
- 07 9月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
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.
-
- 06 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
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
-
- 05 9月, 2006 5 次提交
-
-
由 Bruce Momjian 提交于
Christopher Kings-Lynne
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Albe Laurenz
-
由 Bruce Momjian 提交于
Christopher Kings-Lynne
-
由 Bruce Momjian 提交于
Simon Riggs
-
- 04 9月, 2006 4 次提交
-
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
is only invoked on completed WAL segments, period --- there's no 'by default' about it.
-
- 03 9月, 2006 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
--- was part of autovacuum default 'on' patch that was reverted, but we want this part. Peter Eisentraut
-
由 Bruce Momjian 提交于
possible autovacuum use.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
multiple columns Susanne Ebrecht
-
由 Tom Lane 提交于
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.
-
- 02 9月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
"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
-
由 Bruce Momjian 提交于
Sven Suursoho
-
- 31 8月, 2006 1 次提交
-
-
由 Tom Lane 提交于
Bernd Helmle
-
- 30 8月, 2006 1 次提交
-
-
由 Tom Lane 提交于
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.
-