| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
default"
> or "NO SCROLL is the default", it will be rejected as incorrect. The
> reason is that the default behavior is different from either of these,
> as is explained in the NOTES section.
Ok, so *that's* where the bit about the query plan being simple enough.
Based on that, ISTM that it should be premissable for us to decide that
a cursor requiring a sort isn't "simple enough" to support SCROLL.
In any case, here's a patch that makes the non-standard behavior easier
for people to find.
Jim C. Nasby
|
| |
|
|
|
|
| |
David Fetter
|
| |
|
|
|
|
|
|
|
| |
single column dump that has a \. value, so the load works properly. I
also added documentation describing this issue.
Backpatch to 8.1.X.
|
|
|
|
|
|
| |
integrity actions.
Stephan Szabo
|
|
|
|
| |
has been that way for a long time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DROP CONSTRAINT
This form drops constraints on a table. Currently, constraints on tables
are not required to have unique names, so there may be more than one
constraint matching the specified name. All matching constraints will be
dropped.
To my knowledge, it is no longer possible to create constraints with the
same name for the same relation. When you create a constraint and specify
the same name explictly, an error is raised. Implicit constraint creation
won't choose an existing name either and up to now you could not rename a
constraint. Renaming works with the patch I sent in a few hours ago but this
patch as well won't allow constraints with identical names on the same
relation.
The attached patch thus removes the note in the docs.
Joachim Wieland
|
| |
|
| |
|
|
|
|
| |
elsewhere.
|
| |
|
|
|
|
| |
referential integrity relationships.
|
|
|
|
| |
Andreas Seltenreich
|
| |
|
|
|
|
|
| |
held by means of role membership, rather than directly. Per discussion
and bug fix of a couple weeks ago.
|
|
|
|
| |
rather than British. Patch from Michael Fuhr.
|
|
|
|
|
| |
documentation. Mostly add some <xref>s, fix a few typos, and
document that zlib is required in the installation docs.
|
| |
|
|
|
|
| |
affected types of objects.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
emit when given the --clean option, in favor of individual DROP ROLE
commands. The old technique could not possibly work in 8.1, and was
never a very good idea anyway IMHO. The DROP ROLE approach has the
defect that the DROPs will fail for roles that own objects or have
privileges, but perhaps we can improve that later.
|
|
|
|
| |
renamed to --log-file for clarity.
|
|
|
|
| |
SQL option spelling.
|
|
|
|
|
|
|
| |
relocated after installation. We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config. This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.
|
|
|
|
|
|
|
|
| |
maintenance.sgml.
Robert Treat
[ Also fix create domain markup.]
|
|
|
|
| |
David Fetter
|
| |
|
|
|
|
| |
appears in the REINDEX ref page.
|
|
|
|
|
|
| |
for procedural languages. This replaces the hard-wired table I had
originally proposed as a stopgap solution. For the moment, the initial
contents only include languages shipped with the core distribution.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as per my recent proposal. For now the template data is hard-wired in
proclang.c --- this should be replaced later by a new shared system
catalog, but we don't want to force initdb during 8.1 beta. This change
lets us cleanly load existing dump files even if they contain outright
wrong information about a PL's support functions, such as a wrong path
to the shared library or a missing validator function. Also, we can
revert the recent kluges to make pg_dump dump PL support functions that
are stored in pg_catalog.
While at it, I removed the code in pg_regress that replaced $libdir
with a hardcoded path for temporary installations. This is no longer
needed given our support for relocatable installations.
|
|
|
|
| |
Suggestion by Darcy Buskermolen, reworded by me.
|
|
|
|
| |
per Bruce's suggestion.
|
| |
|
| |
|
|
|
|
|
|
|
| |
erroring out as it has done for the last couple weeks. Document that this
form is now ignored because indexes can't usefully have different owners
from their parent tables. Fix pg_dump to not generate ALTER OWNER commands
for indexes.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
other stuff; change \du and \dg to be role-aware (Stefan Kaltenbrunner).
Also make tab completion fetch the list of GUC variables from pg_settings
instead of having a hard-wired copy of the list (Tom Lane).
|
|
|
|
| |
Alvaro.
|
|
|
|
|
| |
only composite types as we did in 8.0. Per discussion with Martijn
van Oosterhout.
|
|
|
|
|
|
| |
CPPFLAGS, CFLAGS, CFLAGS_SL, LDFLAGS, LDFLAGS_SL, and LIBS. Change it
so that invoking pg_config with no arguments reports all available
information, rather than just giving an error message. Per discussion.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was not especially critical before, but it is now that we track
ownership dependencies --- the dependency for the rowtype *must* shift
to the new owner. Spotted by Bernd Helmle.
Also fix a problem introduced by recent change to allow non-superusers
to do ALTER OWNER in some cases: if the table had a toast table, ALTER
OWNER failed *even for superusers*, because the test being applied would
conclude that the new would-be owner had no create rights on pg_toast.
A side-effect of the fix is to disallow changing the ownership of indexes
or toast tables separately from their parent table, which seems a good
idea on the whole.
|
|
|
|
|
| |
Original patch by Hans-Juergen Schoenig, revisions by Karel Zak
and Tom Lane.
|
| |
|
|
|
|
| |
editorialization.
|