| Age | Commit message (Collapse) | Author |
|---|
|
paragraph about what that means.
|
|
|
|
I weeded out some really old information along the way.
FAQ_AIX needs separate consideration and will be dealt with later.
|
|
|
|
built-in array_agg. Per suggestion from Robert Haas.
|
|
db_user_namespace is enabled.
Also document this limitation.
|
|
|
|
database (only for SSL connections, obviously).
|
|
instead of just relying on the root certificate file to be present.
|
|
Now "\help WITH" works and there will be a separate WITH(7) man page.
|
|
table is less abstract. Most common implementations were already
mentioned in the text.
|
|
slow-running queries.
Takahiro Itagaki
|
|
getpeerucred() function.
Author: Garick Hamlin <ghamlin@isc.upenn.edu>
|
|
conflict resolution.
|
|
locate the target row, if the cursor was declared with FOR UPDATE or FOR
SHARE. This approach is more flexible and reliable than digging through the
plan tree; for instance it can cope with join cursors. But we still provide
the old code for use with non-FOR-UPDATE cursors. Per gripe from Robert Haas.
|
|
procedure support: it's possible to get confused because exported procedures
have two different addresses. Per Andrew Chernow.
|
|
array_agg() and unnest(). We could drop it entirely in the future,
but let's keep it for a release or two as a compatibility assist.
|
|
entries, we don't have to do two builds here as well.
|
|
another section if required by the platform (instead of the old way of
building them in section "l" and always transforming them to the
platform-specific section).
This speeds up the installation on common platforms, and it avoids some
funny business with the man page tools and build process.
|
|
anyelement. This lacks the WITH ORDINALITY option, as well as the multiple
input arrays option added in the most recent SQL specs. But it's still a
pretty useful subset of the spec's functionality, and it is enough to
allow obsoleting contrib/intagg.
|
|
|
|
Rearrange the documentation a bit now that array_agg and xmlagg have similar
semantics and issues.
best of Robert Haas, Jeff Davis, Peter Eisentraut
|
|
Add config parameter "sslverify" to control the verification. Default
is to do full verification.
Clean up some old SSL code that never really worked.
|
|
We don't actually use this anywhere, but it might come in handy for dealing
with SELECT/WITH/TABLE.
It works with both the old and the new man page target (for some value of
"works").
|
|
man page tools.
|
|
man page tools somewhat.
|
|
function as a special case.
This version still has the suspicious behavior of returning null for an
empty array (rather than zero), but this may need a wholesale revision of
empty array behavior, currently under discussion.
Jim Nasby, Robert Haas, Peter Eisentraut
|
|
Greg Sabino Mullane
|
|
specifically, we can input either the "format with designators" or the
"alternative format", and we can output the former when IntervalStyle is set
to iso_8601.
Ron Mayer
|
|
different locales. This is just syntactical sweetener over --lc-collate and
--lc-ctype. Per discussion.
While at it, properly document --lc-ctype and --lc-collate in SGML docs,
which apparently were forgotten (or purposefully ommited?) when they were
created.
|
|
VACUUM reset them to false rather than trying to clean 'em up during DROP.
|
|
("there might be triggers") rather than an exact count. This is necessary
catalog infrastructure for the upcoming patch to reduce the strength of
locking needed for trigger addition/removal. Split out and committed
separately for ease of reviewing/testing.
In passing, also get rid of the unused pg_class columns relukeys, relfkeys,
and relrefs, which haven't been maintained in many years and now have no
chance of ever being maintained (because of wishing to avoid locking).
Simon Riggs
|
|
If the latter doesn't exist, automatically recreate it. (We don't do
this for pg_xlog, though, per discussion.)
Jonah Harris
|
|
(It's always worked like this, but we never documented it before.)
|
|
from DateStyle, and create a new interval style that produces output matching
the SQL standard (at least for interval values that fall within the standard's
restrictions). IntervalStyle is also used to resolve the conflict between the
standard and traditional Postgres rules for interpreting negative interval
input.
Ron Mayer
|
|
|
|
as much of it as lives in its default tablespace) to a new tablespace.
Guillaume Lelarge, with some help from Bernd Helmle and Tom Lane
|
|
if their source or target types match the pattern (using the same definition
of "match" as \dT does). Per recent discussion.
|
|
postgresql.conf 'ssl' section.
|
|
backpatch to 8.3.X.
|
|
tool chain. With some polishing, this might help us get rid of our ancient
and crufty man page build mechanism.
|
|
Author: Robert Haas <robertmhaas@gmail.com>
|
|
|
|
|
|
almost certainly represents user error. Per a gripe from Sebastian Böhm
and subsequent discussion.
|
|
data type. This patch takes the approach of allowing an optional hyphen after
each group of four hex digits.
Author: Robert Haas <robertmhaas@gmail.com>
|
|
|
|
Brendan Jurd
|
|
|
|
upon requests from backends, rather than on a fixed 500msec cycle. (There's
still throttling logic to ensure it writes no more often than once per
500msec, though.) This should result in a significant reduction in stats file
write traffic in typical scenarios where the stats are demanded only
infrequently.
This approach also means that the former difficulty with changing
stats_temp_directory on-the-fly has gone away, so remove the caution about
that as well as the thrashing we did to minimize the trouble window.
In passing, also fix pgstat_report_stat() so that we will send a stats
message if we have function call stats but not table stats to report;
this fixes a bug in the recent patch to support function-call stats.
Martin Pihlak
|
