| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
7.4.26.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to unload and re-load the library.
The difficulty with unloading a library is that we haven't defined safe
protocols for doing so. In particular, there's no safe mechanism for
getting out of a "hook" function pointer unless libraries are unloaded
in reverse order of loading. And there's no mechanism at all for undefining
a custom GUC variable, so GUC would be left with a pointer to an old value
that might or might not still be valid, and very possibly wouldn't be in
the same place anymore.
While the unload and reload behavior had some usefulness in easing
development of new loadable libraries, it's of no use whatever to normal
users, so just disabling it isn't giving up that much. Someday we might
care to expend the effort to develop safe unload protocols; but even if
we did, there'd be little certainty that every third-party loadable module
was following them, so some security restrictions would still be needed.
Back-patch to 8.2; before that, LOAD was superuser-only anyway.
Security: unprivileged users could crash backend. CVE not assigned yet
|
| | |
|
| |
|
|
|
| |
This was changed in 8.2 but the documentation was not corrected.
Per gripe from Sam Mason.
|
| | |
|
| |
|
|
| |
decade ago. Backpatch to release 7.4.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
as per my recent proposal. release.sgml itself is now just a stub that should
change rarely; ideally, only once per major release to add a new include line.
Most editing work will occur in the release-N.N.sgml files. To update a back
branch for a minor release, just copy the appropriate release-N.N.sgml
file(s) into the back branch.
This commit doesn't change the end-product documentation at all, only the
source layout. However, it makes it easy to start omitting ancient information
from newer branches' documentation, should we ever decide to do that.
|
| |
|
|
| |
fields without putting a space between. Per gripe from Rick Schumeyer.
|
| |
|
|
| |
further backpatch.
|
| |
|
|
| |
data structure, rather than silently truncating them. Andrew Gierth
|
| | |
|
| | |
|
| |
|
|
| |
in the incorrect order, per bug 4593. Backpatch to 8.3.X.
|
| | |
|
| |
|
|
|
|
|
| |
to reindex GiST indexes:
If you were running a previous 8.X.X release, REINDEX all GiST
indexes after the upgrade.
|
| |
|
|
|
| |
various documentation, since those lists are now dead/deprecated.
Point to pgsql-bugs and/or pgsql-hackers as appropriate.
|
| |
|
|
|
|
| |
of autovacuum_max_workers parameter is.
Per discussion with Alvaro.
|
| |
|
|
| |
with warning against setting it too high.
|
| |
|
|
| |
Per discussion.
|
| |
|
|
|
| |
misdocumented as not being implemented. In reality it has worked since
the release of 8.2.
|
| | |
|
| |
|
|
| |
Greg Sabino Mullane
|
| |
|
|
| |
backpatch to 8.3.X.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
recursion when we are unable to convert a localized error message to the
client's encoding. We've been over this ground before, but as reported by
Ibrar Ahmed, it still didn't work in the case of conversion failures for
the conversion-failure message itself :-(. Fix by installing a "circuit
breaker" that disables attempts to localize this message once we get into
recursion trouble.
Patch all supported branches, because it is in fact broken in all of them;
though I had to add some missing translations to the older branches in
order to expose the failure in the particular test case I was using.
|
| |
|
|
| |
Per gripe from Bill Thoen.
|
| | |
|
| |
|
|
| |
Pointed out by Daniel Migowski.
|
| |
|
|
| |
backpatch to 8.3.X. Also fix markup that had just one bullet.
|
| |
|
|
| |
SGML source but in the actual web/pdf viewer...
|
| |
|
|
|
|
|
| |
for building on MSVC, and that the free distribution is enough
(no need for the enterprise version).
Per gripe from Martin Zaun.
|
| |
|
|
| |
(Extracted from fast-insert patch, since it ought to be back-patched)
|
| |
|
|
| |
ITAGAKI Takahiro
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
require SELECT privilege as well, since you normally need to read existing
column values within such commands. This behavior is according to spec,
but we'd never documented it before. Per gripe from Volkan Yazici.
|
| | |
|
| |
|
|
| |
auto-configure properly for libxslt present or not.
|
| | |
|
| |
|
|
| |
it now lives (per discussion). Leave the other FAQs alone for now.
|
| | |
|
| |
|
|
|
|
| |
version ones, to make it clear to users just browsing the notes
that there are a lot more changes available from whatever version
they are at than what's in the minor version release notes.
|
| | |
|
| | |
|
| |
|
|
| |
on developer.postgresql.org is going away.
|
| | |
|
| | |
|
