- 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 提交于
-
- 09 9月, 2006 4 次提交
-
-
由 Tom Lane 提交于
remove the old isbn_issn module which is about to be obsoleted by EAN13. contrib/isn is by Germán Méndez Bravo. Our thanks to Garrett A. Wollman for having written the original isbn_issn module.
-
由 Tom Lane 提交于
than before. Albe Laurenz (but editorialized heavily by me, so if it doesn't work it's my fault).
-
由 Tom Lane 提交于
I had thought this code could be left alone, but I was wrong: as-is it's failing to recognize when to use ALL for table privileges in 8.2.
-
由 Tom Lane 提交于
to a relation on the nullable side of an outer join. I had removed this during the outer join planning rewrite a few months ago ... I think I intended to put it somewhere else, but forgot ...
-
- 08 9月, 2006 6 次提交
-
-
由 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.
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 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.
-
由 Bruce Momjian 提交于
-
- 07 9月, 2006 10 次提交
-
-
由 Bruce Momjian 提交于
-
由 Michael Meskes 提交于
Float/Long aliasing doesn't work on all architecures.
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Andrew Dunstan
-
由 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.
-
由 Tom Lane 提交于
Per buildfarm results.
-
- 06 9月, 2006 12 次提交
-
-
由 Teodor Sigaev 提交于
pointers are int64, but warnings are emitted for position info in error messages in parser, so, just cast it to int32
-
由 Bruce Momjian 提交于
Michael Glaesemann
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Marko Kreen
-
由 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
-
由 Tom Lane 提交于
fix suggestion from Peter.
-
由 Teodor Sigaev 提交于
-
由 Teodor Sigaev 提交于
'GIN FailedAssertions on Itanium2 with Intel compiler' in pgsql-hackers, http://archives.postgresql.org/pgsql-hackers/2006-08/msg01914.php
-
由 Teodor Sigaev 提交于
Per discussion http://archives.postgresql.org/pgsql-hackers/2006-08/msg01409.php
-
由 Tom Lane 提交于
dbase, dbmirror, fulltextindex, mac, userlock; or abandoned: mSQL-interface, tips.
-
- 05 9月, 2006 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
Added some interval checks to regression suite.
-
由 Michael Meskes 提交于
Fixed ecpglib trying to read one character after end-of-string. Fixed port number setting in regression suite.
-