| Age | Commit message (Collapse) | Author |
|---|
|
Instead, foreign tables are treated just like views: permissions can
be granted using GRANT privilege ON [TABLE] foreign_table_name TO role,
and revoked similarly. GRANT/REVOKE .. FOREIGN TABLE is no longer
supported, just as we don't support GRANT/REVOKE .. VIEW. The set of
accepted permissions for foreign tables is now identical to the set for
regular tables, and views.
Per report from Thom Brown, and subsequent discussion.
|
|
Strip leading and trailing whitespace and replace interior whitespace
by a single space. This avoids problems with the index generator
producing duplicate index entries for terms that differ only in
whitespace.
Commit dca30da3433c40b5f92f1704c496cda052decef9 actually fixed all the
indexterm elements that would cause this problem at the moment, but in
case it sneaks in again, we're set.
|
|
This test should now work in any database with UTF8 encoding, regardless
of the database's default locale. The former restriction was really
"doesn't work if default locale is C", and that was because of not handling
mbstowcs/wcstombs correctly.
|
|
This patch is almost entirely cosmetic --- mostly cleaning up a lot of
neglected comments, and fixing code layout problems in places where the
patch made lines too long and then pgindent did weird things with that.
I did find a bug-of-omission in equalTupleDescs().
|
|
|
|
Without this, adding an attribute to a typed table with an inheritance
child fails, which is surprising.
Noah Misch, with minor changes by me.
|
|
This syntax allows a standalone table to be made into a typed table,
or a typed table to be made standalone. This is possibly a mildly
useful feature in its own right, but the real motivation for this
change is that we need it to make pg_upgrade work with typed tables.
This doesn't actually fix that problem, but it's necessary
infrastructure.
Noah Misch
|
|
Curiously, it was already documented in ALTER TYPE ADD ATTRIBUTE, but
not here.
|
|
This allows the usual rules for assigning a collation to a local variable
to be overridden. Per discussion, it seems appropriate to support this
rather than forcing all local variables to have the argument-derived
collation.
|
|
Peter Eisentraut
|
|
Anything including Visual Studio 2010 compilers is not yet
supported for building on Windows.
|
|
Also refactor things a little bit so that the same methods for setting
test locale and encoding can be used everywhere.
|
|
|
|
The latest openjade packages for Ubuntu 10.10 seg fault when building
our documentation.
Josh Berkus
|
|
Per a suggestion from Josh Kupershmidt, though I modified his patch
quite a lot.
|
|
This involves getting the character classification and case-folding
functions in the regex library to use the collations infrastructure.
Most of this work had been done already in connection with the upper/lower
and LIKE logic, so it was a simple matter of transposition.
While at it, split out these functions into a separate source file
regc_pg_locale.c, so that they can be correctly labeled with the Postgres
project's license rather than the Scriptics license. These functions are
100% Postgres-written code whereas what remains in regc_locale.c is still
mostly not ours, so lumping them both under the same copyright notice was
getting more and more misleading.
|
|
"Unusable" collations are those not matching the current database's
encoding. The former behavior inconsistently showed such collations
some of the time, depending on the details of the pattern argument.
|
|
As noted by Thom Brown, this confuses the DocBook index processor; it
fails to merge entries that differ only in whitespace, and sorts them
unexpectedly as well. Seems like a toolchain bug, but I'm not going to
hold my breath waiting for a fix.
Note: easiest way to find these is to look for double spaces in HTML.index.
|
|
Per a discussion with Gavin Flower. This barely scratches the surface
of potential WITH (something RETURNING) use cases, of course, but it's
one of the simplest compelling examples I can think of.
|
|
|
|
Gabriele Bartolini
|
|
Erik Rijkers
|
|
Joey Adams, per gripe from Ramanujam. Review by myself and Tom Lane.
|
|
|
|
|
|
This means one less thing to configure when setting up synchronous
replication, and also avoids some ambiguity around what the behavior
should be when the settings of these variables conflict.
Fujii Masao, with additional hacking by me.
|
|
This improves compatibility with external toolchains, such as those used
by some documentation translation tools.
Gabriele Bartolini
|
|
|
|
Gianni Ciolli, reviewed by Noah Misch
|
|
This isn't applicable on Windows, and the internal link to the
psql documentation should be more than sufficient.
Susanne Ebrecht
|
|
Susanne Ebrecht and me
|
|
This mostly involves making it work with the objectaddress.c framework,
which does most of the heavy lifting. In that vein, change
GetForeignDataWrapperOidByName to get_foreign_data_wrapper_oid and
GetForeignServerOidByName to get_foreign_server_oid, to match the
pattern we use for other object types.
Robert Haas and Shigeru Hanada
|
|
|
|
than replication_timeout (a new GUC) milliseconds. The TCP timeout is often
too long, you want the master to notice a dead connection much sooner.
People complained about that in 9.0 too, but with synchronous replication
it's even more important to notice dead connections promptly.
Fujii Masao and Heikki Linnakangas
|
|
This can do various source code checks that are not appropriate for
either the build or the regression tests. Currently: duplicate_oids,
SGML syntax and tabs check, NLS syntax check.
|
|
We already had links to the GUC variables that control it.
|
|
Unlike <xref>, this actually works.
|
|
|
|
Kevin Grittner
|
|
Susanne Ebrecht
|
|
The underlying problem that caused this phenomenon was fixed by commit
92f4786fa9b730fd12cbfe973eb96addc6e98924.
|
|
In addition, correct the entry for pg_object_description, and some other
minor cleanup.
|
|
This is pretty minimal but covers the bare facts.
|
|
Temporarily move some of the alpha release note disclaimers into the regular
release notes, for the sake of alpha5.
|
|
|
|
-r no_indicator
-r prepare
-r questionsmarks
|
|
Add some new items and some additional details to existing items, mostly
by cribbing from the 9.1alpha notes. Some additional clarifications and
corrections elsewhere, and a few typo fixes.
|
|
On closer inspection, that two-element initcond value seems to have been
a little white lie to avoid explaining the full behavior of float8_accum.
But if people are going to expect the examples to be exactly correct,
I suppose we'd better explain. Per comment from Thom Brown.
|
|
The description of the initcond value for the built-in avg(float8)
aggregate has been wrong since it was written. Noted by Disc Magnet.
|
|
|
