| Age | Commit message (Collapse) | Author |
|
Error pointed out by Fujii Masao, though not his patch.
|
|
|
|
Brendan Jurd
|
|
The GRANT reference page failed to mention that the USAGE privilege
allows modifying associated user mappings, although this was already
documented on the CREATE/ALTER/DROP USER MAPPING pages.
|
|
|
|
The new formatting matches what we do for COPY.
Per a complaint from Bruce Momjian.
|
|
|
|
In particular, we are now more explicit about the fact that you may need
wal_sync_method=fsync_writethrough for crash-safety on some platforms,
including MaxOS X. There's also now an explicit caution against assuming
that the default setting of wal_sync_method is either crash-safe or best
for performance.
|
|
Actual behaviour did not match documented behaviour and we have agreed
that it should be the docs that change.
Spotted by Bernd Helmle
|
|
Per Tatsuhito Kasahara.
|
|
|
|
There are numerous methods by which a Perl or Tcl function can subvert
the behavior of another such function executed later; for example, by
redefining standard functions or operators called by the target function.
If the target function is SECURITY DEFINER, or is called by such a
function, this means that any ordinary SQL user with Perl or Tcl language
usage rights can do essentially anything with the privileges of the target
function's owner.
To close this security hole, create a separate Perl or Tcl interpreter for
each SQL userid under which plperl or pltcl functions are executed within
a session. However, all plperlu or pltclu functions run within a session
still share a single interpreter, since they all execute at the trust
level of a database superuser anyway.
Note: this change results in a functionality loss when libperl has been
built without the "multiplicity" option: it's no longer possible to call
plperl functions under different userids in one session, since such a
libperl can't support multiple interpreters in one process. However, such
a libperl already failed to support concurrent use of plperl and plperlu,
so it's likely that few people use such versions with Postgres.
Security: CVE-2010-3433
|
|
Erik Rijkers
|
|
8.0.26, and 7.4.30.
|
|
directory.
Per report from Harald Armin Massa.
|
|
Per report from Harald Armin Massa
|
|
title, per suggestion from Ian Barwick.
|
|
Command synopses using <cmdsynopsis> with multiple variants previously used
<sbr> to break lines between variants. The new man page toolchain introduced
in 9.0 makes a mess out of that, and that markup was probably wrong all along,
because <sbr> is supposed to break lines within a synopsis, not between them.
So fix that by using multiple <cmdsynopsis> elements inside <refsynopsisdiv>.
backpatched to 9.0
|
|
|
|
These are just cosmetic and don't seem worth back-patching far.
I put them into 9.0 just because it was trivial to do so.
|
|
|
|
for git. Change other references from cvs to git as well.
|
|
|
|
|
|
|
|
copy-editing.
|
|
|
|
when fld is of composite type. Per discussion of bug #5644 from Valentine
Gogichashvili.
|
|
Also, add cross-reference from pg_shadow.passwd to pg_authid.rolpasswd and
fix a bit of markup I muffed in my previous commit.
Per discussion with Josh Kupershmidt.
|
|
it doesn't work.
Backpatch to 9.0.X.
|
|
Per discussion with Josh Kupershmidt.
|
|
Backpatch to 9.0.X.
|
|
It isn't, now that we ship the docs as loose files rather than a sub-tarball.
Also adjust the wording in a couple of places to make the lists of required
software read more consistently.
|
|
- remove excessive table cells
- moving function parameters into function tags rather than having
them being considered separate
- add return type column on XML2 contrib module functions list and
removing return types from function
- add table header to XML2 contrib parameter table
Thom Brown
Backpatch to 9.0.X.
|
|
|
|
|
|
Per KOIZUMI Satoru.
|
|
type. Per KOIZUMI Satoru.
|
|
Per discussion.
|
|
and contains operators.
|
|
|
|
Spotted by Dmitriy Igrishin. Back-patch to 8.2, which is when the PREPARE
statement was improved to allow parameter types to be omitted.
|
|
which is perhaps not a terribly good spot for it but there doesn't seem to be
a better place. Also add a source-code comment pointing out a couple reasons
for having a separate lock file. Per suggestion from Greg Smith.
|
|
of constraints.
Kevin Grittner
|
|
questionable reliability; information moved to a wiki:
http://wiki.postgresql.org/wiki/Incrementally_Updated_Backups
Backpatch to 9.0.
|
|
While at it, copy-edit the description of prefix-match marker support in
synonym dictionaries, and clarify the description of the default unaccent
dictionary a bit more.
|
|
|
|
|
|
|
|
Note: as usual, bug fixes that were also applied in back branches are not
considered material to include in a new major release's notes.
|