- 10 9月, 2006 1 次提交
-
-
由 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.
-
- 09 9月, 2006 3 次提交
-
-
由 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 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Michael Meskes 提交于
Float/Long aliasing doesn't work on all architecures.
-
由 Michael Meskes 提交于
-
由 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 4 次提交
-
-
由 Bruce Momjian 提交于
Michael Glaesemann
-
由 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 提交于
'GIN FailedAssertions on Itanium2 with Intel compiler' in pgsql-hackers, http://archives.postgresql.org/pgsql-hackers/2006-08/msg01914.php
-
- 05 9月, 2006 11 次提交
-
-
由 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.
-
由 Bruce Momjian 提交于
Bruce, Michael Glaesemann
-
由 Tom Lane 提交于
position_in_unique_constraint (column newly added per SQL2003). Greg Mullane
-
由 Bruce Momjian 提交于
second scan of table). Gregory Stark
-
由 Bruce Momjian 提交于
Magnus Hagander
-
由 Tom Lane 提交于
the target relation(s). There might be some cases where we could discard the pending event instead, but for the moment a conservative approach seems sufficient. Per report from Markus Schiltknecht and subsequent discussion.
-
由 Bruce Momjian 提交于
of 'S', and the views were not checking for table visibility with regards to temporary tables and sequences. Greg Sabino Mullane
-
由 Bruce Momjian 提交于
some platforms.
-
由 Tom Lane 提交于
working in a multibyte encoding. This fixes the problems exhibited in bug #1931 and other reports of ILIKE misbehavior in UTF8 encoding. It's a pretty grotty solution though --- should rethink how to do it after we install better locale support, someday.
-
- 04 9月, 2006 5 次提交
-
-
由 Peter Eisentraut 提交于
Author: Victor Wagner <vitus@cryptocom.ru>
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
cascaded first to days and only what is leftover into seconds. This seems to satisfy the principle of least surprise given the general conversion to three-part interval values --- it was an oversight that these cases weren't dealt with in 8.1. Michael Glaesemann
-
由 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 提交于
-
- 03 9月, 2006 5 次提交
-
-
由 Tom Lane 提交于
PGPROC array into snapshots, and use this information to avoid visits to pg_subtrans in HeapTupleSatisfiesSnapshot. This appears to solve the pg_subtrans-related context swap storm problem that's been reported by several people for 8.1. While at it, modify GetSnapshotData to not take an exclusive lock on ProcArrayLock, as closer analysis shows that shared lock is always sufficient. Itagaki Takahiro and Tom Lane
-
由 Michael Meskes 提交于
Added another regression test and fixed tcp test.
-
由 Bruce Momjian 提交于
multiplication/division queries like select '41 mon 10:00:00'::interval / 10 as "pos". Report from Michael Glaesemann
-
由 Bruce Momjian 提交于
fetch/move in scan.l.
-
由 Bruce Momjian 提交于
Report from Josh Tolley.
-