| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
a multicolumn-capable index AM *must* support nulls in index columns
after the first one.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
function body (and other properties) as a function in the language
is created. This generalizes ad hoc code that already existed for
the built-in languages.
The validation now happens after the pg_proc tuple of the new function
is created, so it is possible to define recursive SQL functions.
Add some regression test cases that cover bogus function definition
attempts.
|
| | |
|
| |
|
|
| |
I took the opportunity to remove the pg_proc.proistrusted field.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
GUC support. It's now possible to set datestyle, timezone, and
client_encoding from postgresql.conf and per-database or per-user
settings. Also, implement rollback of SET commands that occur in a
transaction that later fails. Create a SET LOCAL var = value syntax
that sets the variable only for the duration of the current transaction.
All per previous discussions in pghackers.
|
| |
|
|
| |
about TO/FROM direction in several places.
|
| |
|
|
|
| |
to C at run-time, and providing alternative output files for different
sort orders.
|
| |
|
|
| |
that we don't upcase the others.
|
| |
|
|
|
|
|
| |
underlying function; but cause psql's \do to show the underlying
function's comment if the operator has no comment of its own, to preserve
the useful functionality of the original behavior. Also, implement
COMMENT ON SCHEMA. Patch from Rod Taylor.
|
| | |
|
| |
|
|
| |
but the basic capability seems to work.
|
| |
|
|
|
| |
Re-add warning if the locale prevents LIKE-optimization. Done within
initdb now.
|
| |
|
|
|
|
|
|
| |
to reset session userid to the originally-authenticated name. Also,
relax SET SESSION AUTHORIZATION to allow specifying one's own username
even if one is not superuser, so as to avoid unnecessary error messages
when loading a pg_dump file that uses this command. Per discussion from
several months ago.
|
| | |
|
| |
|
|
|
| |
I concluded that RENAME should require CREATE privilege on the namespace
as well as ownership of the table.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Update has_table_privilege functions to cope with schema-qualified
names in the same way as nextval() and others.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
per pghackers discussion. Add some more typsanity tests, and clean
up some problems exposed thereby (broken or missing array types for
some built-in types). Also, clean up loose ends from unknownin/out
patch.
|
| | |
|
| |
|
|
|
|
| |
no objections.
Joe Conway
|
| |
|
|
|
|
|
|
|
|
| |
The attached patch allows views to have default values. You can't
specify a default value within a CREATE VIEW statement, it must be
done using ALTER TABLE ... ALTER COLUMN ... SET DEFAULT after the
view has already been created. Most of the hard work was done by
Tom Lane, I just patched pg_dump and updated the documentation.
Neil Conway <neilconway@rogers.com>
|
| |
|
|
|
|
|
|
| |
Please note I have no way to test this. Docbook doesn't like my
cygwin setup.
--
Rod Taylor
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
capabilities of specifying time zones as intervals per SQL9x.
Put refentrytitle contents on the same line as the tag.
Otherwise, leading whitespace is propagated into the product, which
(at least) messes up the ToC layout.
Remove (some) docinfo tags containing dates. Best to omit if the dates
are not accurate; maybe use CVS dates instead or leave them out.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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...
|
| |
|
|
| |
_RETURN now, since there's no need to keep 'em unique anymore.
|
| |
|
|
|
|
|
|
|
|
| |
(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.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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 >.
|
| |
|
|
|
|
| |
selected as the creation target namespace; to make that happen, you
must explicitly set search_path that way. This makes initdb a hair
more complex but seems like a good safety feature.
|
