| Age | Commit message (Collapse) | Author |
|---|
|
|
|
column, OUT and INOUT added.
Guillaume LELARGE
|
|
cursors. Patch from Joachim Wieland, review and ediorialization by Neil
Conway. The view lists cursors defined by DECLARE CURSOR, using SPI, or
via the Bind message of the frontend/backend protocol. This means the
view does not list the unnamed portal or the portal created to implement
EXECUTE. Because we do list SPI portals, there might be more rows in
this view than you might expect if you are using SPI implicitly (e.g.
via a procedural language).
Per recent discussion on -hackers, the query string included in the
view for cursors defined by DECLARE CURSOR is based on
debug_query_string. That means it is not accurate if multiple queries
separated by semicolons are submitted as one query string. However,
there doesn't seem a trivial fix for that: debug_query_string
is better than nothing. I also changed SPI_cursor_open() to include
the source text for the portal it creates: AFAICS there is no reason
not to do this.
Update the documentation and regression tests, bump the catversion.
|
|
|
|
|
|
can convey information to clients on constraint violation.
|
|
an array of regtype, rather than an array of OIDs. This is likely to
be more useful to user, and the type OID can easily be obtained by
casting a regtype value to OID. Per suggestion from Tom.
Update the documentation and regression tests, and bump the catversion.
|
|
data type is unspecified or is declared to be "unknown", the type will
be inferred from the context in which the parameter is used. This was
already possible for protocol-level prepared statements.
|
|
permissions on the functions and operators contained in the opclass.
Since we already require superuser privilege to create an operator class,
there's no expansion-of-privilege hazard here, but if someone were to get
the idea of building an opclass containing functions that need security
restrictions, we'd better warn them off. Also, change the permission
checks from have-execute-privilege to have-ownership, and then comment
them all out since they're dead code anyway under the superuser restriction.
|
|
type definition. Because use of a type's I/O conversion functions isn't
access-checked, CREATE TYPE amounts to granting public execute permissions
on the functions, and so allowing it to anybody means that someone could
theoretically gain access to a function he's not supposed to be able to
execute. The parameter-type restrictions already enforced by CREATE TYPE
make it fairly unlikely that this oversight is meaningful in practice,
but still it seems like a good idea to plug the hole going forward.
Also, document the implicit grant just in case anybody gets the idea of
building I/O functions that might need security restrictions.
|
|
certainly. Per report from George Woodring.
|
|
|
|
of the CREATE CONVERSION syntax, for consistency with the other SQL
reference pages.
|
|
Replace the former ad-hoc implementation used in the regression tests.
Joachim Wieland
|
|
access information about the prepared statements that are available
in the current session. Original patch from Joachim Wieland, various
improvements by Neil Conway.
The "statement" column of the view contains the literal query string
sent by the client, without any rewriting or pretty printing. This
means that prepared statements created via SQL will be prefixed with
"PREPARE ... AS ", whereas those prepared via the FE/BE protocol will
not. That is unfortunate, but discussion on -patches did not yield an
efficient way to improve this, and there is some merit in returning
exactly what the client sent to the backend.
Catalog version bumped, regression tests updated.
|
|
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00151.php for the
complete plan.
|
|
|
|
|
|
|
|
documentation.
Michael Fuhr
|
|
|
|
single column dump that has a \. value, so the load works properly. I
also added documentation describing this issue.
|
|
(previously we only did = and <> correctly). Also, allow row comparisons
with any operators that are in btree opclasses, not only those with these
specific names. This gets rid of a whole lot of indefensible assumptions
about the behavior of particular operators based on their names ... though
it's still true that IN and NOT IN expand to "= ANY". The patch adds a
RowCompareExpr expression node type, and makes some changes in the
representation of ANY/ALL/ROWCOMPARE SubLinks so that they can share code
with RowCompareExpr.
I have not yet done anything about making RowCompareExpr an indexable
operator, but will look at that soon.
initdb forced due to changes in stored rules.
|
|
and add logic to try max_fsm_pages up to 200000, plus accompanying minor
docs changes.
|
|
|
|
|
|
postgresql.conf.sample too.
|
|
|
|
of having no password.
|
|
modify the previous \password patch to use it instead of depending
on a not-officially-exported function. Per discussion.
|
|
SET.
|
|
|
|
Backpatch to 8.1.X.
|
|
Fix example for day and hours interval subtraction for new computation
method.
Update interval examples to display zero seconds, which is our default.
Backpatch to 8.1.X.
|
|
Per my recent proposal. I ended up basing the implementation on the
existing mechanism for enforcing valid join orders of IN joins --- the
rules for valid outer-join orders are somewhat similar.
|
|
|
|
password encryption. Also alter createuser command to the same effect.
|
|
Patch from Pavel Stehule, minor fixups by myself.
|
|
Also minor improvements to 8.1.1 release notes.
|
|
integrity actions.
Stephan Szabo
|
|
has been that way for a long time.
|
|
|
|
datestyle parameter of the new cluster accordingly.
|
|
|
|
|
