| Age | Commit message (Collapse) | Author |
|---|
|
statistics.
Takahiro Itagaki
|
|
documentation.
|
|
the postmaster. They are only used in backend processes, so it's just
a matter of re-labeling the GUCs.
|
|
and change auto_explain's custom GUC variables to be named auto_explain.xxx
not just explain.xxx. Per discussion in connection with the
pg_stat_statements patch, it seems like a good idea to have the convention
that custom variable classes are named the same as their defining module.
Committing separately since this should happen regardless of what happens
with pg_stat_statements itself.
|
|
|
|
frame clause, as appears to be required by the fine print in the SQL spec.
Per discussion with Pavel, not doing so risks user confusion.
|
|
so that user-defined window functions are possible. For the moment you'll
have to write them in C, for lack of any interface to the WindowObject API
in the available PLs, but it's better than no support at all.
There was some debate about the best syntax for this. I ended up choosing
the "it's an attribute" position --- the other approach will inevitably be
more work, and the likely market for user-defined window functions is
probably too small to justify it.
|
|
patch. This includes the ability to force the frame to cover the whole
partition, and the ability to make the frame end exactly on the current row
rather than its last ORDER BY peer. Supporting any more of the full SQL
frame-clause syntax will require nontrivial hacking on the window aggregate
code, so it'll have to wait for 8.5 or beyond.
|
|
per Hitoshi Harada.
|
|
Hitoshi Harada, with some kibitzing from Heikki and Tom.
|
|
useful yet, but I'm tired of re-merging this aspect of the window functions
patch.
|
|
This doesn't do any remote or external things yet, but it gives modules
like plproxy and dblink a standardized and future-proof system for
managing their connection information.
Martin Pihlak and Peter Eisentraut
|
|
recent gripe that the info is hard to find.
|
|
|
|
|
|
per recent discussions. In passing this also fixes a couple of bugs in
the previous variadic-parameters patch.
|
|
various facilities.
|
|
surprised/confused some users.
|
|
shared_buffers and wal_buffers, not size in bytes. Per discussion.
|
|
confusing.
|
|
|
|
result in hopefully-less-confusing error messages when the new definition
isn't compatible with the old; minor other cleanup.
|
|
and certificate revokation list by using connection parameters or environment
variables.
Original patch by Mark Woodward, heavily reworked by Alvaro Herrera and
Magnus Hagander.
|
|
and its maximum value from 1000 to 10000. ALTER TABLE SET STATISTICS
similarly now allows a value up to 10000. Per discussion.
|
|
vacuuming (it's not), say "database-wide VACUUM" instead of "full-database
VACUUM" in the relevant hint messages. Also, document the permissions needed
to do this. Per today's discussion.
|
|
to the gettext domain name, to simplify parallel installations.
Also, rename set_text_domain() to pg_bindtextdomain(), because that is what
it does.
|
|
|
|
composite column. Might help cut down on future questions...
|
|
of autovacuum_max_workers parameter is.
Per discussion with Alvaro.
|
|
with warning against setting it too high.
|
|
SGML-escaping.
|
|
Robert Haas
|
|
|
|
Pavel Stehule, with some tweaks by Peter Eisentraut
|
|
|
|
|
|
|
|
|
|
|
|
the basic representational details (typlen, typalign, typbyval, typstorage)
to be copied from an existing type rather than listed explicitly in the
CREATE TYPE command. The immediate reason for this is to provide a simple
solution for add-on modules that want to define types represented as int8,
float4, or float8: as of 8.4 the appropriate PASSEDBYVALUE setting is
platform-specific and so it's hard for a SQL script to know what to do.
This patch fixes the contrib/isn breakage reported by Rushabh Lathia.
|
|
|
|
PL/pgSQL has much to do with SQL/PSM.
|
|
that the presented list of equivalent operations is meant to be the
primary definition of what it does. Per comment from Guillaume Smet.
|
|
page build target. This covers from-source, Debian, and Fedora
installation variants.
|
|
|
|
misdocumented as not being implemented. In reality it has worked since
the release of 8.2.
|
|
libpq. As noted by Peter, adding this variable created a risk of unexpected
connection failures when talking to older server versions, and since it
doesn't do anything you can't do with PGOPTIONS, it doesn't seem really
necessary. Removing it does occasion a few extra lines in pg_regress.c,
but saving a getenv() call per libpq connection attempt is perhaps worth
that anyway.
|
|
The information on why the shared libraries are built the way they are
was not relevant to end users and has been made a mailing list archive
link in Makefile.shlib.
|
|
Jim Cox and Peter Eisentraut
|
|
|
