| Age | Commit message (Collapse) | Author |
|---|
|
the default. This setting enables constraint exclusion checks only for
appendrel members (ie, inheritance children and UNION ALL arms), which are
the cases in which constraint exclusion is most likely to be useful. Avoiding
the overhead for simple queries that are unlikely to benefit should bring
the cost down to the point where this is a reasonable default setting.
Per today's discussion.
|
|
debug_query_string; this allows current_query() to be more accurate;
docs updated; per idea from Tom
|
|
not include postgres.h nor anything else it doesn't directly need. Add
#includes to calling files as needed to compensate. Per my proposal of
yesterday.
This should be noted as a source code change in the 8.4 release notes,
since it's likely to require changes in add-on modules.
|
|
to pass the full username@realm string to the authentication instead of
just the username. This makes it possible to use pg_ident.conf to authenticate
users from multiple realms as different database users.
|
|
authentication options to be set in pg_hba.conf on a per-line basis, to
override the defaults set in postgresql.conf.
|
|
like previous patch did.
Per note from Tom Lane
|
|
clarity.
|
|
Fix \do and trigger display for the patch too.
|
|
|
|
various documentation, since those lists are now dead/deprecated.
Point to pgsql-bugs and/or pgsql-hackers as appropriate.
|
|
particular this allows EmitWarningsOnPlaceholders messages to show up in the
postmaster log by default. Update elog.h comment to make it clearer what INFO
is for, and fix one example in the SGML docs that was misusing it. Per my
gripe of yesterday.
|
|
|
|
performing dumps and restores in accordance with a security policy that
forbids logging in directly as superuser, but instead specifies that you
should log into an admin account and then SET ROLE to the superuser.
In passing, clean up some ugly and mostly-broken code for quoting shell
arguments in pg_dumpall.
Benedek László, with some help from Tom Lane
|
|
Jun Kuwamura
|
|
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
|
|
|
|
|
