| Age | Commit message (Collapse) | Author |
|---|
|
Alvaro Herrera
|
|
|
|
This is new in 9.3devel.
|
|
|
|
Andres Freund
|
|
Erwin Brandstetter
|
|
LANGUAGE 'plpgsql' no longer works. The single quotes need to be
removed.
Erwin Brandstetter
|
|
Split log shipping speed improvement and fail-over speed improvement items.
Per request from Simon
|
|
|
|
Already fixed in back branch.
|
|
Move commit_delay, fix Zoltan's name, and adjust range type histogram
text.
|
|
|
|
Typo fix from David Fetter.
|
|
|
|
|
|
More to go.
|
|
Forgotten in previous commit.
|
|
No links added yet.
|
|
suggested by Jov
|
|
Only adjusted the user-exposed messages and documentation, not all
source code comments.
|
|
KaiGai Kohei
|
|
The return type of PQgetssl() was changed from SSL* to void* a long time
ago, but the documentation was not updated.
|
|
This changes the behavior of the start and stop actions to exit
successfully if the server was already started or stopped.
This changes the default behavior of the start action: Before, if the
server was already running, it would print a message and succeed. Now,
that situation will result in an error. When running in idempotent
mode, no message is printed and pg_ctl exits successfully.
It was considered to just make the idempotent behavior the default and
only option, but pg_upgrade needs the old behavior.
|
|
To do this, we add an additional object access hook type,
OAT_FUNCTION_EXECUTE.
KaiGai Kohei
|
|
The old web site link no longer worked, and some information was
outdated.
|
|
Remove references to "one click", as we're not supposed to call
them that anymore.
|
|
This wasn't addressed in the original patch, but it doesn't take very
much additional code to cover the case, so let's get it done.
Since pg_trgm 1.1 hasn't been released yet, I just changed the definition
of what's in it, rather than inventing a 1.2.
|
|
Marti Raudsepp.
|
|
This works by extracting trigrams from the given regular expression,
in generally the same spirit as the previously-existing support for
LIKE searches, though of course the details are far more complicated.
Currently, only GIN indexes are supported. We might be able to make
it work with GiST indexes later.
The implementation includes adding API functions to backend/regex/
to provide a view of the search NFA created from a regular expression.
These functions are meant to be generic enough to be supportable in
a standalone version of the regex library, should that ever happen.
Alexander Korotkov, reviewed by Heikki Linnakangas and Tom Lane
|
|
KaiGai Kohei, with comment and doc wordsmithing by me
|
|
There's been some confusion expressed about this point, so clarify.
Extended version of a patch by David Wheeler.
|
|
|
|
This allows convenient re-execution of commands.
Will Leinweber, reviewed by Peter Eisentraut, Daniel Farina, and Tom Lane
|
|
Dickson S. Guedes
|
|
Laurenz Albe
|
|
Security: CVE-2013-1899, CVE-2013-1901
|
|
|
|
This will hopefully be easier to use than pg_config for users who are
already used to the pkg-config interface. It also works better for
multi-arch installations.
reviewed by Tom Lane
|
|
|
|
|
|
The JSON parser is converted into a recursive descent parser, and
exposed for use by other modules such as extensions. The API provides
hooks for all the significant parser event such as the beginning and end
of objects and arrays, and providing functions to handle these hooks
allows for fairly simple construction of a wide variety of JSON
processing functions. A set of new basic processing functions and
operators is also added, which use this API, including operations to
extract array elements, object fields, get the length of arrays and the
set of keys of a field, deconstruct an object into a set of key/value
pairs, and create records from JSON objects and arrays of objects.
Catalog version bumped.
Andrew Dunstan, with some documentation assistance from Merlin Moncure.
|
|
I changed this in commit fd15dba543247eb1ce879d22632b9fdb4c230831, but
missed the fact that the SGML documentation of the function specified
exactly what it did. Well, one of the two places where it's specified
documented that --- probably I looked at the other place and thought
nothing needed to be done. Sync the two places where encode() and
decode() are described.
|
|
Covers commits through today. Not back-patching into back branches
yet, since this is just for people to review in advance.
|
|
Fixes by me, per griping by Thom Brown.
|
|
The main change here is to call security_compute_create_name_raw()
rather than security_compute_create_raw(). This ups the minimum
requirement for libselinux from 2.0.99 to 2.1.10, but it looks
like most distributions will have picked that up before 9.3 is out.
KaiGai Kohei
|
|
This event takes place just before ddl_command_end, and is fired if and
only if at least one object has been dropped by the command. (For
instance, DROP TABLE IF EXISTS of a table that does not in fact exist
will not lead to such a trigger firing). Commands that drop multiple
objects (such as DROP SCHEMA or DROP OWNED BY) will cause a single event
to fire. Some firings might be surprising, such as
ALTER TABLE DROP COLUMN.
The trigger is fired after the drop has taken place, because that has
been deemed the safest design, to avoid exposing possibly-inconsistent
internal state (system catalogs as well as current transaction) to the
user function code. This means that careful tracking of object
identification is required during the object removal phase.
Like other currently existing events, there is support for tag
filtering.
To support the new event, add a new pg_event_trigger_dropped_objects()
set-returning function, which returns a set of rows comprising the
objects affected by the command. This is to be used within the user
function code, and is mostly modelled after the recently introduced
pg_identify_object() function.
Catalog version bumped due to the new function.
Dimitri Fontaine and Álvaro Herrera
Review by Robert Haas, Tom Lane
|
|
|
|
Commit bc5334d8679c428a709d150666b288171795bd76 accidentally
included a second <variablelist> tag for a new list item.
|
|
KaiGai Kohei
|
|
If required, recovery.conf can now be located outside of the data directory.
Server needs read/write permissions on this directory.
|
