- 21 4月, 2002 6 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
different privilege bits (might as well make use of the space we were wasting on padding). EXECUTE and USAGE bits for procedures, languages now are separate privileges instead of being overlaid on SELECT. Add privileges for namespaces and databases. The GRANT and REVOKE commands work for these object types, but we don't actually enforce the privileges yet...
-
由 Tatsuo Ishii 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
Use flex flags -CF. Pass the to-be-scanned string around as StringInfo type, to avoid querying the length repeatedly. Clean up some code and remove lex-compatibility cruft. Escape backslash sequences inline. Use flex-provided yy_scan_buffer() function to set up input, rather than using myinput().
-
- 20 4月, 2002 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
_RETURN now, since there's no need to keep 'em unique anymore.
-
由 Tom Lane 提交于
(tgrelid, tgname). This provides an additional check on trigger name uniqueness per-table (which was already enforced by the code anyway). With this change, RelationBuildTriggers will read the triggers in order by tgname, since it's scanning using this index. Since a predictable trigger ordering has been requested for some time, document this behavior as a feature. Also document that rules fire in name order, since yesterday's changes to pg_rewrite indexing cause that too.
-
- 19 4月, 2002 4 次提交
-
-
由 Tom Lane 提交于
per previous discussion.
-
由 Tom Lane 提交于
DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause, similar to TRIGGER syntaxes. To allow loading of existing pg_dump files containing COMMENT ON RULE, the COMMENT code will still accept the old syntax --- but only if the target rulename is unique across the whole database.
-
由 Bruce Momjian 提交于
< without using PL/PgSQL EXECUTE, needs cached plan invalidation > without using PL/PgSQL EXECUTE, needs cache prevention/invalidation
-
由 Bruce Momjian 提交于
> o Abort all, some or, no SET changes made in an aborted transaction
-
- 18 4月, 2002 22 次提交
-
-
由 Bruce Momjian 提交于
> o Abort all or commit all SET changes made in an aborted transaction
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> o Allow Java server-side programming, http://pljava.sourceforge.net > [java]
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Rod is Rod Taylor <rbt@zort.ca>
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Cache most recent query plan(s) (Neil) [prepare] > * Neil is Neil Conway <nconway@klamath.dyndns.org>
-
由 Bruce Momjian 提交于
> using a sequential scan for highest/lowest values (Oleg)
-
由 Bruce Momjian 提交于
Add to DROP COLUMN description.
-
由 Bruce Momjian 提交于
> o Abort SET changes made in aborted transactions (?)
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Add BETWEEN ASYMMETRIC/SYMMETRIC (Christopher) > * Christopher is Christopher Kings-Lynne <chriskl@familyhealth.com.au>
-
由 Bruce Momjian 提交于
> * Add BSD-licensed qsort() for Solaris
-
由 Bruce Momjian 提交于
> o Allow SHOW to output as a query result, like EXPLAIN
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Try flex flags -Cf and -CF to see if performance improves
-
由 Bruce Momjian 提交于
> * Add utility to compute accurate random_page_cost value
-
由 Tom Lane 提交于
an 'opclass owner' column in pg_opclass. Nothing is done with it at present, but since there are plans to invent a CREATE OPERATOR CLASS command soon, we'll probably want DROP OPERATOR CLASS too, which suggests that a notion of ownership would be a good idea.
-
由 Bruce Momjian 提交于
> * Allow easy display of usernames in a group
-
- 17 4月, 2002 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
qualified operator names directly, for example CREATE OPERATOR myschema.+ ( ... ). To qualify an operator name in an expression you need to write OPERATOR(myschema.+) (thanks to Peter for suggesting an escape hatch). I also took advantage of having to reformat pg_operator to fix something that'd been bugging me for a while: mergejoinable operators should have explicit links to the associated cross-data-type comparison operators, rather than hardwiring an assumption that they are named < and >.
-