| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the code underlying pg_get_expr() is not secure against malformed
input, and can't practically be made so, we need to prevent miscreants
from feeding arbitrary data to it. We can do this securely by declaring
pg_get_expr() to take a new datatype "pg_node_tree" and declaring the
system catalog columns that hold nodeToString output to be of that type.
There is no way at SQL level to create a non-null value of type pg_node_tree.
Since the backend-internal operations that fill those catalog columns
operate below the SQL level, they are oblivious to the datatype relabeling
and don't need any changes.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Backpatch to 9.0.X.
|
|
|
|
| |
Josh Berkus
|
|
|
|
|
|
| |
default is low because of pg_clog file removal.
Backpatch to 9.0.X.
|
|
|
|
| |
Pavel Stehule, reviewed by me.
|
|
|
|
|
| |
This is mostly about grammar, style, and presentation, though I did find
a few small factual errors.
|
|
|
|
| |
We already mentioned xid wraparound.
|
| |
|
|
|
|
| |
Per Thom Brown.
|
|
|
|
|
|
|
|
|
|
| |
Per gripe from Fujii Masao, though this is not exactly his proposed patch.
Categorize as DEVELOPER_OPTIONS and set context PGC_SIGHUP, as per Fujii,
but set the default to LOG because higher values aren't really sensible
(see the code for trace_recovery()). Fix the documentation to agree with
the code and to try to explain what the variable actually does. Get rid
of no-op calls trace_recovery(LOG), which accomplish nothing except to
demonstrate that this option confuses even its author.
|
|
|
|
| |
at end of files.
|
| |
|
| |
|
| |
|
|
|
|
| |
Boszormenyi Zoltan.
|
| |
|
|
|
|
| |
Robert Haas, per gripe from Erik Rijkers
|
|
|
|
| |
Kevin Grittner, with markup adjustments.
|
|
|
|
|
|
| |
look at a function but don't wish to fire up an editor.
Pavel Stehule, reviewed by Jan Urbanski
|
|
|
|
|
| |
Update the documentation, and back out a few ill-considered changes
whose folly I failed to realize for failure to read the documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to reliably remove all leftover temporary relation
files on cluster startup without reference to system catalogs or WAL;
therefore, we no longer include temporary relations in XLOG_XACT_COMMIT
and XLOG_XACT_ABORT WAL records.
Since these changes require including a backend ID in each
SharedInvalSmgrMsg, the size of the SharedInvalidationMessage.id
field has been reduced from two bytes to one, and the maximum number
of connections has been reduced from INT_MAX / 4 to 2^23-1. It would
be possible to remove these restrictions by increasing the size of
SharedInvalidationMessage by 4 bytes, but right now that doesn't seem
like a good trade-off.
Review by Jaime Casanova and Tom Lane.
|
|
|
|
|
|
|
|
| |
functions to the core XML code. Per discussion, the former depends on
XMLOPTION while the others do not. These supersede a version previously
offered by contrib/xml2.
Mike Fowler, reviewed by Pavel Stehule
|
|
|
|
| |
Thom Brown
|