+ linkend="functions-admin-backup-table">pg_start_backup()
+ and pg_stop_backup() to support non-exclusive backups
+ (Magnus Hagander)
2016-07-26 [d8411a6c8] Allow functions that return sets of tuples to return sim
-->
- Allow functions that return sets of tuples to return simple NULLs
- (Andrew Gierth, Tom Lane)
+ Allow functions that return sets of tuples to return simple
+ NULLs (Andrew Gierth, Tom Lane)
In the context of SELECT FROM function(...), a function
that returned a set of composite values was previously not allowed
- to return a plain NULL value as part of the set. Now that is
- allowed and interpreted as a row of NULLs. This avoids corner-case
- errors with, for example, unnesting an array of composite values.
+ to return a plain NULL value as part of the set.
+ Now that is allowed and interpreted as a row of NULLs.
+ This avoids corner-case errors with, for example, unnesting an
+ array of composite values.
2016-08-03 [a3c7a993d] Make INSERT-from-multiple-VALUES-rows handle targetlist
-->
- Fully support array subscripts and field selections in the target
- column list of an INSERT with
- multiple VALUES rows (Tom Lane)
+ Fully support array subscripts and field selections in the
+ target column list of an INSERT with multiple
+ VALUES rows (Tom Lane)
- This change allows command tags for SELECT etc. to
- correctly report tuple counts larger than 4 billion. So will
- PL/pgSQL's GET DIAGNOSTICS ... ROW_COUNT command.
+ This change allows command tags, e.g. SELECT, to
+ correctly report tuple counts larger than 4 billion. This also
+ applies to PL/pgSQL's GET DIAGNOSTICS ... ROW_COUNT
+ command.
2015-11-28 [8d32717b6] Avoid doing encoding conversions by double-conversion vi
-->
- Avoid doing encoding conversions by double-conversion
- through MULE_INTERNAL encoding (Tom Lane)
+ Avoid doing encoding conversions by converting through the
+ MULE_INTERNAL encoding (Tom Lane)
- Previously, many conversions for Cyrillic and Central European
- single-byte encodings were done by converting to a
+ Previously, many conversions for Cyrillic and Central
+ European single-byte encodings were done by converting to a
related MULE_INTERNAL coding scheme and then to the
- destination encoding. Aside from being inefficient, this meant that
- when the conversion encountered an untranslatable character, the error
- message would confusingly complain about failure to convert to or
- from MULE_INTERNAL, rather than the user-visible
- encodings.
+ destination encoding. Aside from being inefficient, this meant
+ that when the conversion encountered an untranslatable character,
+ the error message would confusingly complain about failure to
+ convert to or from MULE_INTERNAL, rather than the
+ user-visible encoding.
- Previously, the foreign join pushdown infrastructure left the question
- of security entirely up to individual foreign data wrappers, but it
- would be easy for an FDW to inadvertently open up subtle security
- holes that way. So, make it the core code's job to determine which
- role ID will access each table, and don't attempt join pushdown unless
- it's the same for all relevant relations.
+ Previously, the foreign join pushdown infrastructure left the
+ question of security entirely up to individual foreign data
+ wrappers, but it would be too easy for an
FDW to+ inadvertently open up subtle security hole. So, make it the core
+ code's job to determine which role ID will access each table,
+ and do not attempt join pushdown unless the role is the same for
+ all relevant relations.
2015-11-27 [92e38182d] COPY (INSERT/UPDATE/DELETE .. RETURNING ..)
-->
- Allow COPY to copy the output of
- an INSERT/UPDATE/DELETE
+ Allow COPY to copy the output of an
+ INSERT/UPDATE/DELETE
... RETURNING query (Marko Tiikkaja)
- Previously, an intermediate CTE had to be written to get this result.
+ Previously, an intermediate
CTE had to be written to+ get this result.
- This command allows a database object to be marked as depending on an
- extension, so that it will automatically go away if the extension is
- dropped (without needing CASCADE). But the object is not
- part of the extension, and thus for example will be dumped separately
+ This command allows a database object to be marked as depending
+ on an extension, so that it will be automatically dropped if
+ the extension is dropped (without needing CASCADE).
+ However, the object is not part of the extension, and thus will
+ b
e dumped separately by
pg_dump.
Make ALTER object SET SCHEMA do nothing
when the object is already in the requested schema, rather than
- throwing an error as it historically has for most object types (Marti
- Raudsepp)
+ throwing an error as it historically has for most object types
+ (Marti Raudsepp)
2015-12-31 [0dab5ef39] Fix ALTER OPERATOR to update dependencies properly.
-->
- Add options to ALTER OPERATOR to change the
- selectivity functions associated with an existing operator
+ Add options to ALTER OPERATOR to allow changing
+ the selectivity functions associated with an existing operator
(Yury Zhuravlev)
2015-07-29 [2cd40adb8] Add IF NOT EXISTS processing to ALTER TABLE ADD COLUMN
-->
- Add an
- COLUMN (Fabrízio de Royes Mello)
+ Add an
+ ADD COLUMN (Fabrízio de Royes Mello)
2016-03-10 [fcb4bfddb] Reduce lock level for altering fillfactor
-->
- Reduce the lock strength needed by ALTER TABLE when
- setting fillfactor and autovacuum-related relation options
+ Reduce the lock strength needed by ALTER TABLE
+ when setting fillfactor and autovacuum-related relation options
(Fabrízio de Royes Mello, Simon Riggs)
2016-03-23 [473b93287] Support CREATE ACCESS METHOD
-->
- Introduce CREATE ACCESS METHOD to allow extensions to
- create index access methods (Alexander Korotkov, Petr Jelínek)
+ Introduce CREATE ACCESS METHOD to allow extensions
+ to create index access methods (Alexander Korotkov, Petr
+ Jelínek)
-->
Add a CASCADE option to CREATE
- EXTENSION, to automatically create extensions it depends on
- (Petr Jelínek)
-
-
-
-
-
- Remove the
- long-deprecated CREATEUSER/NOCREATEUSER
- options from CREATE ROLE and allied commands (Tom Lane)
-
-
- CREATEUSER actually meant SUPERUSER, for
- ancient backwards-compatibility reasons. That's been a constant
- source of confusion for people who (reasonably) expect it to
- mean CREATEROLE. It's been deprecated for ten years
- now, so fix the problem by removing it.
+ EXTENSION to automatically create extensions it depends
+ on (Petr Jelínek)
2015-10-05 [b943f502b] Have CREATE TABLE LIKE add OID column if any LIKEd table
-->
- Make CREATE TABLE ... LIKE include an OID column if any
- source table has one (Bruce Momjian)
+ Make CREATE TABLE ... LIKE include an OID
+ column if any source table has one (Bruce Momjian)
2015-12-16 [f27a6b15e] Mark CHECK constraints declared NOT VALID valid if creat
-->
- If a CHECK constraint is declared NOT VALID in
- a table creation command, automatically mark it valid (Amit Langote,
- Amul Sul)
+ If a CHECK constraint is declared NOT VALID
+ in a table creation command, automatically mark it as valid
+ (Amit Langote, Amul Sul)
- This matches the longstanding behavior of FOREIGN KEY
- constraints.
+ This possible because the table has no existing rows. This matches
+ the longstanding behavior of FOREIGN KEY constraints.
2016-03-25 [c94959d41] Fix DROP OPERATOR to reset oprcom/oprnegate links to the
-->
- Fix DROP OPERATOR to
- clear pg_operator.oprcom
- and pg_operator.oprnegate links to the
- dropped operator (Roma Sokolov)
+ Fix DROP OPERATOR to clear
+ pg_operator.oprcom and
+ pg_operator.oprnegate links to
+ the dropped operator (Roma Sokolov)
- Formerly such links were left as-is, which could pose a problem in
- the somewhat unlikely event that the dropped operator's OID was
- reused for another operator.
+ Formerly such links were left as-is, which could pose a problem
+ in the somewhat unlikely event that the dropped operator's
+ OID was reused for another operator.
2016-04-16 [c34df8a00] Disallow creation of indexes on system columns (except f
-->
- Disallow creation of indexes on system columns, except for OID
- (David Rowley)
+ Disallow creation of indexes on system columns, except for
+ OID columns (David Rowley)
- Such indexes were never considered supported, and would very possibly
- misbehave since the system might change the system-column fields of a
- tuple without updating indexes. But there was no error check to
- prevent them from being created.
+ Such indexes were never considered supported, and would very
+ possibly misbehave since the system might change the system-column
+ fields of a tuple without updating indexes. However, previously
+ there were no error checks to prevent them from being created.
Formerly, many security-sensitive functions contained hard-wired
checks that would throw an error if they were called by a
- non-superuser role. This forced use of superuser roles for some
- relatively pedestrian tasks. The hard-wired error checks are now gone
- in favor of making
initdb revoke the default- public EXECUTE privilege on these functions. This allows
- installations to choose to grant usage of such functions to trusted
- roles that need not have full superuser privilege.
-
-
-
-
-
- Treat role names beginning with pg_ as reserved
- (Stephen Frost)
-
-
- User creation of such role names is now disallowed. This prevents
- conflicts with built-in roles created by
initdb.+ non-superuser role. This forced the use of superuser roles for
+ some relatively pedestrian tasks. The hard-wired error checks
+ are now gone in favor of making
initdb revoke the+ default public EXECUTE privilege on these functions.
+ This allows installations to choose to grant usage of such
+ functions to trusted roles that need not have full superuser
+ privilege.
2016-04-08 [7a542700d] Create default roles
-->
- Create some built-in roles that
- can be used to grant access to what were previously superuser-only
- functions (Stephen Frost)
+ Create some built-in roles
+ that can be used to grant access to what were previously
+ superuser-only functions (Stephen Frost)
-->
Allow omitting one or both boundaries in an array slice specifier,
- for example array_col[3:]
- (Yury Zhuravlev)
+ e.g. array_col[3:] (Yury Zhuravlev)
Omitted boundaries are taken as the upper or lower limit of the
- corresponding array subscript. This allows simpler specification of
- many common use-cases.
+ corresponding array subscript. This allows simpler specification
+ for many common use-cases.
2016-03-16 [a70e13a39] Be more careful about out-of-range dates and timestamps.
-->
- Be more careful about out-of-range dates and timestamps
- (Vitaly Burovoy)
+ Be more careful about out-of-range dates and timestamps (Vitaly
+ Burovoy)
- This change prevents unexpected out-of-range errors
- for timestamp with time zone values very close to the
- implementation limits. Previously, the same value might be
- accepted or not depending on the timezone setting,
+ This change prevents unexpected out-of-range errors for
+ timestamp with time zone values very close to the
+ implementation limits. Previously, the same value might
+ be accepted or not depending on the timezone setting,
meaning that a dump and reload could fail on a value that had been
- accepted when presented. Now the limits are enforced according to
- the equivalent UTC time, not local time, so as to be independent
- of timezone.
+ accepted when presented. Now the limits are enforced according
+ t
o the equivalent UTC time, not local time, so as to+ be independent of timezone.
2016-03-30 [50861cd68] Improve portability of I/O behavior for the geometric ty
-->
- In the geometric data types, make sure that infinity and NaN
- component values are treated consistently during input and output
- (Tom Lane)
+ In the geometric data types, make sure that infinity
+ and NaN component values are treated consistently
+ during input and output (Tom Lane)
- Such values will now always print the same way as they would in a
- simple float8 column, and be accepted the same way on input
- as well. Previously the behavior was somewhat platform-dependent.
+ Such values will now always print the same as they would in
+ a simple float8 column, and be accepted the same way
+ on input. Previously the behavior was platform-dependent.
2016-06-27 [6734a1cac] Change predecence of phrase operator.
-->
- Improve full-text search to support searching for phrases, that is,
- lexemes appearing adjacent to each other in a specific order, or with
- a specified distance between them
- (Teodor Sigaev, Oleg Bartunov, Dmitry Ivanov)
+ Improve full-text search to support searching for phrases, that
+ is, lexemes appearing adjacent to each other in a specific order,
+ or with a specified distance between them (Teodor Sigaev, Oleg
+ Bartunov, Dmitry Ivanov)
- A phrase-search query can be specified in tsquery input
- using the new operators <-> and
- <N>. The former means that
- the lexemes before and after it must appear adjacent to each other in
- that order. The latter means they must be exactly N
- lexemes apart.
-
-
-
-
-
- Fix text search parser to allow leading digits in email
- and host tokens (Artur Zakirov)
-
-
- In most cases this will result in few changes in the parsing of text.
- But if you have data where such addresses occur frequently, it may be
- worth rebuilding dependent tsvector columns and indexes, so
- that addresses of this form will be found properly by text searches.
+ A phrase-search query can be specified in tsquery
+ input using the new operators <-> and
+ <N>. The former means
+ that the lexemes before and after it must appear adjacent to
+ each other in that order. The latter means they must be exactly
+ N lexemes apart.
2016-03-17 [f4ceed6ce] Improve support of Hunspell
-->
- Upgrade the ispell dictionary to handle modern Hunspell
- files and support more languages (Artur Zakirov)
+ Upgrade the ispell dictionary to handle modern
+
Hunspell files and support more languages+ (Artur Zakirov)
2015-10-30 [12c9a0400] Implement lookbehind constraints in our regular-expressi
-->
- Implement lookbehind constraints in regular expressions
- (Tom Lane)
+ Implement look-behind constraints in regular expressions (Tom Lane)
- A lookbehind constraint is like a lookahead constraint in that it
- consumes no text; but it checks for existence (or nonexistence) of a
- match ending at the current point in the string, rather than one
- starting at the current point. Similar features exist in many other
- regular-expression engines.
+ A look-behind constraint is like a lookahead constraint in that it
+ consumes no text; but it checks for existence (or nonexistence)
+ of a match ending at the current point in the string, rather
+ than one starting at the current point. Similar features exist
+ in many other regular-expression engines.
2015-09-16 [b44d92b67] Sync regex code with Tcl 8.6.4.
-->
- In regular expressions, if an apparent three-digit octal
- escape \nnn would exceed 377 (255
- decimal), assume it is a two-digit octal escape instead (Tom Lane)
+ In regular expressions, if an apparent three-digit octal escape
+ \nnn would exceed 377 (255 decimal),
+ assume it is a two-digit octal escape instead (Tom Lane)
- This makes the behavior match current Tcl releases.
+ This makes the behavior match current
Tcl releases.
2015-11-07 [c5e86ea93] Add "xid <> xid" and "xid <> int4" operators.
-->
- Add xid <> xid
- and xid <> int4 operators,
- for consistency with the corresponding = operators
- (Michael Paquier)
+ Add xid <> xid and xid
+ <> int4 operators, for consistency
+ with the corresponding = operators (Michael Paquier)
2016-04-06 [0b62fd036] Add jsonb_insert
-->
- Add jsonb_insert() function to insert a new element into
- a jsonb array, or a not-previously-existing key into
- a jsonb object (Dmitry Dolgov)
+ Add
+ linkend="functions-json-processing-table">jsonb_insert()
+ function to insert a new element into a jsonb array,
+ or a not-previously-existing key into a jsonb object
+ (Dmitry Dolgov)
- For example, sind() measures its argument in
- degrees, whereas sin() measures in radians.
- These functions go to some lengths to deliver exact results for values
- where an exact result can be expected, such
- as sind(30) = 0.5 exactly.
+ For example,
+ linkend="functions-math-trig-table">sind()
+ measures its argument in degrees, whereas sin()
+ measures in radians. These functions go to some lengths to
+ deliver exact results for values where an exact result can be
+ expected, e.g. sind(30) = 0.5.
2016-01-22 [fd5200c3d] Improve cross-platform consistency of Inf/NaN handling i
-->
- Ensure that trigonometric functions handle infinity and NaN inputs per
- the POSIX standard (Dean Rasheed)
-
-
- The POSIX standard says that these functions should return NaN for NaN
- input, and should throw an error for out-of-range inputs including
- infinity; but previously, our actual behavior varied across platforms.
-
-
-
-
-
- Make extract() behave more reasonably with infinite
- inputs (Vitaly Burovoy)
+ Ensure that trigonometric functions handle infinity
+ and
NaN inputs per the POSIX standard+ (Dean Rasheed)
- Historically the extract() function just returned zero
- given an infinite timestamp, regardless of the given unit name. Make
- it return infinity or -infinity
- as appropriate when the requested field is one that is monotonically
- increasing (e.g, year, epoch), or NULL when it is not (e.g., day,
- hour). Also, throw the expected error for bad unit names.
+ The
POSIX standard says that these functions should+ return NaN for NaN input, and should throw an error for
+ out-of-range inputs including infinity; but previously,
+ our actual behavior varied across platforms.
2016-03-29 [e511d878f] Allow to_timestamp(float8) to convert float infinity to
-->
- Make to_timestamp(float8) convert float infinity to
- timestamp infinity (Vitaly Burovoy)
+ Make to_timestamp(float8) convert float
+ infinity to timestamp infinity (Vitaly
+ Burovoy)
- These are ts_delete(), ts_filter(),
- unnest(), tsvector_to_array(),
- array_to_tsvector(), and a variant
- of setweight() that sets the weight only for specified
- lexeme(s).
+ These are
+ linkend="textsearch-functions-table">ts_delete(),
+ ts_filter(), unnest(),
+ tsvector_to_array(), array_to_tsvector(),
+ and a variant of setweight() that sets the weight
+ only for specified lexeme(s).
2015-09-17 [9acb9007d] Fix oversight in tsearch type check
-->
- Allow ts_stat_sql()
- and tsvector_update_trigger() to operate on values that
- are of types binary-compatible with the expected argument type, not
- just that argument type; for example allow citext
+ Allow ts_stat_sql() and
+ tsvector_update_trigger() to operate on values that
+ are of types binary-compatible with the expected argument type,
+ not just that argument type; for example allow citext
where text is expected (Teodor Sigaev)
2016-02-04 [6819514fc] Add num_nulls() and num_nonnulls() to count NULL argumen
-->
- Add variadic functions num_nulls()
+ Add variadic functions
+ linkend="functions-comparison-func-table">num_nulls()
and num_nonnulls() that count the number of their
- arguments that are null or nonnull (Marko Tiikkaja)
+ arguments that are null or non-null (Marko Tiikkaja)
- An example usage is CHECK(num_nonnulls(a,b,c) = 1) which
- asserts that exactly one of a,b,c isn't NULL. These functions can
- also be used to count the number of null or nonnull elements in an
- array.
+ An example usage is CHECK(num_nonnulls(a,b,c) = 1)
+ which asserts that exactly one of a,b,c is not NULL.
+ These functions can also be used to count the number of null or
+ nonnull elements in an array.
2016-03-18 [3187d6de0] Introduce parse_ident()
-->
- Add function parse_ident() to split a qualified,
- possibly quoted SQL identifier into its parts (Pavel Stehule)
-
-
-
-
-
- In to_char(), do not count a minus sign (when needed) as
- part of the field width for time-related fields (Bruce Momjian)
-
-
- For example, to_char('-4 years'::interval, 'YY') now
- returns -04, rather than -4.
+ Add function
+ linkend="functions-string-other">parse_ident()
+ to split a qualified, possibly quoted
SQL identifier+ into its parts (Pavel Stehule)
2015-10-05 [28b3a3d41] to_number(): allow 'V' to divide by 10^(the number of d
-->
- In to_number(), interpret V as dividing by
- 10 to the power of the number of digits following V
- (Bruce Momjian)
+ In
+ linkend="functions-formatting-table">to_number(),
+ interpret V as dividing by 10 to the power of the
+ number of digits following V (Bruce Momjian)
- This makes it operate in an inverse fashion to to_char().
+ This makes it operate in an inverse fashion to
+ to_char().
- This avoids the need to write an explicit cast in most cases where
- the argument isn't a simple literal constant.
+ This avoids the need to write an explicit cast in most cases
+ where the argument is not a simple literal constant.
2016-02-20 [53874c522] Add pg_size_bytes() to parse human-readable size strings
-->
- Add pg_size_bytes() function to convert human-readable
- size strings to numbers (Pavel Stehule, Vitaly Burovoy, Dean Rasheed)
+ Add
+ linkend="functions-admin-dbsize">pg_size_bytes()
+ function to convert human-readable size strings to numbers (Pavel
+ Stehule, Vitaly Burovoy, Dean Rasheed)
- This function converts strings like those produced
- by pg_size_pretty() into sizes in bytes. An example
+ This function converts strings like those produced by
+ pg_size_pretty() into sizes in bytes. An example
usage is SELECT oid::regclass FROM pg_class WHERE
pg_total_relation_size(oid) > pg_size_bytes('10 GB').
2015-11-06 [8a1fab36a] pg_size_pretty: Format negative values similar to positi
-->
- In pg_size_pretty(), format negative numbers similarly
- to positive ones (Adrian Vondendriesch)
+ In
+ linkend="functions-admin-dbsize">pg_size_pretty(),
+ format negative numbers similarly to positive ones (Adrian
+ Vondendriesch)
2015-07-02 [10fb48d66] Add an optional missing_ok argument to SQL function curr
-->
- Add an optional missing_ok argument to
- the current_setting() function (David Christensen)
+ Add an optional
missing_ok argument to the
+ linkend="functions-admin-set-table">current_setting()
+ function (David Christensen)
This allows avoiding an error for an unrecognized parameter name;
- instead the result is NULL.
+ instead the result is NULL.
2016-08-07 [8a8c6b538] Fix crash when pg_get_viewdef_name_ext() is passed a non
-->
- Change various catalog-inspection functions to return NULL for
- invalid input (Michael Paquier)
+ Change various catalog-inspection functions to return
+ NULL for invalid input (Michael Paquier)
- pg_get_viewdef() now returns NULL if given an invalid
- view OID, and several similar functions likewise return NULL for
+
+ linkend="functions-info-catalog-table">pg_get_viewdef()
+ now returns NULL if given an invalid view OID,
+ and several similar functions likewise return NULL for
bad input. Previously, such cases usually led to cache
lookup failed errors, which are not meant to occur in
user-facing cases.
2016-08-02 [dd5eb805d] Remove unused arguments from pg_replication_origin_xact_
-->
- Fix pg_replication_origin_xact_reset() to not have any
- arguments (Fujii Masao)
+ Fix
+ linkend="pg-replication-origin-xact-reset">pg_replication_origin_xact_reset()
+ to not have any arguments (Fujii Masao)
- The documentation said that it has no arguments, and the C code
- didn't expect any arguments, but the entry in pg_proc
+ The documentation said that it has no arguments, and the C code did
+ not expect any arguments, but the entry in pg_proc
mistakenly specified two arguments.
2015-08-21 [fcdfce682] Detect mismatched CONTINUE and EXIT statements at plpgsq
-->
- In PL/pgSQL,
- detect mismatched CONTINUE and EXIT statements
- while compiling PL/pgSQL functions, rather than at execution
+ In PL/pgSQL, detect mismatched
+ CONTINUE and EXIT statements while
+ compiling PL/pgSQL functions, rather than at execution time
(Jim Nasby)
- Remove PL/pgSQL's feature that suppressed the innermost line
- of CONTEXT for messages emitted by RAISE
- commands (Pavel Stehule)
-
-
- This ancient backwards-compatibility hack was agreed to have outlived
- its usefulness.
-
-
-
-
-
- Extend PL/Python's error-reporting and message-reporting functions to
- allow specifying additional message fields besides the primary error
- message (Pavel Stehule)
+ Extend
PL/Python's error-reporting and+ message-reporting functions to allow specifying additional message
+ fields besides the primary error message (Pavel Stehule)
2016-04-05 [1d2fe56e4] Fix PL/Python for recursion and interleaved set-returnin
-->
- Allow PL/Python functions to call themselves recursively via SPI,
- and fix the behavior when multiple set-returning PL/Python functions
- are called within one query (Alexey Grishchenko, Tom Lane)
+ Allow PL/Python functions to call themselves recursively
+ via
SPI, and fix the behavior when multiple+ set-returning PL/Python functions are called within one query
+ (Alexey Grishchenko, Tom Lane)
2015-11-05 [8c75ad436] Fix memory leaks in PL/Python.
-->
- Fix session-lifespan memory leaks in PL/Python
- (Heikki Linnakangas, Haribabu Kommi, Tom Lane)
+ Fix session-lifespan memory leaks in PL/Python (Heikki Linnakangas,
+ Haribabu Kommi, Tom Lane)
2016-03-02 [e2609323e] Make PL/Tcl require Tcl 8.4 or later.
-->
- Modernize
PL/Tcl to use Tcl's object APIs
- instead of simple strings (Jim Nasby, Karl Lehenbauer)
+ Modernize
PL/Tcl to use Tcl's object
+
APIs instead of simple strings (Jim Nasby, Karl+ Lehenbauer)
-->
In
PL/Tcl, make database-reported errors return- additional information in Tcl's errorCode global variable
- (Jim Nasby, Tom Lane)
+ additional information in Tcl's errorCode global
+ variable (Jim Nasby, Tom Lane)
- This feature follows the Tcl convention for returning auxiliary data
- about an error.
+ This feature follows the Tcl convention for returning auxiliary
+ data about an error.
-->
Fix
PL/Tcl to perform encoding conversion between- the database encoding and UTF-8, which is what Tcl expects (Tom Lane)
+ the database encoding and UTF-8, which is what Tcl
+ expects (Tom Lane)
- Previously, strings were passed through without conversion, leading
- to misbehavior with non-ASCII characters when the database encoding
- isn't UTF-8.
+ Previously, strings were passed through without conversion,
+ leading to misbehavior with non-ASCII characters when
+ the database encoding was not UTF-8.
This commit is also listed under psql and PL/pgSQL
-->
- Introduce a feature in
libpq whereby- the CONTEXT field of messages can be suppressed, either
+ Introduce a feature in
libpq whereby the+ CONTEXT field of messages can be suppressed, either
always or only for non-error messages (Pavel Stehule)
- The default behavior of PQerrorMessage() is now to
- print CONTEXT only for errors. The new
- function PQsetErrorContextVisibility() can be used to
- adjust this.
+ The default behavior of
+ linkend="libpq-pqerrormessage">PQerrorMessage()
+ is now to print CONTEXT
+ only for errors. The new function
+ linkend="libpq-pqseterrorcontextvisibility">PQsetErrorContextVisibility()
+ can be used to adjust this.
2015-11-27 [40cb21f70] Improve PQhost() to return useful data for default Unix-
-->
- Improve
libpq's PQhost() function to- return useful data for default Unix-socket connections (Tom Lane)
+ Improve
libpq's
+ linkend="libpq-pqhost">PQhost() function to return
+ useful data for default Unix-socket connections (Tom Lane)
- Previously it would return NULL if no explicit host specification had
- been given; now it returns the default socket directory path.
+ Previously it would return NULL if no explicit host
+ specification had been given; now it returns the default socket
+ directory path.
2016-02-16 [fc1ae7d2e] Change ecpg lexer to accept comments with line breaks in
-->
- Fix
ecpg's lexer to handle line breaks within comments- starting on preprocessor directive lines (Michael Meskes)
+ Fix
ecpg's lexer to handle line breaks within+ comments starting on preprocessor directive lines (Michael Meskes)
2015-09-14 [d02426029] Check existency of table/schema for -t/-n option (pg_dum
-->
- Add
+ Add
a and
pg_restore (Pavel Stehule)
- This option causes the program to complain if there is no match for
- a or option, rather than
- silently doing nothing.
+ This option causes the program to complain if there is no match
+ for a or option, rather
+ than silently doing nothing.
2016-05-06 [e1b120a8c] Only issue LOCK TABLE commands when necessary
-->
- dump locally-made changes in privilege assignments for system objects
- (Stephen Frost)
+ In
pg_dump, dump locally-made changes in privilege+ assignments for system objects (Stephen Frost)
- While it's always been possible for a superuser to change the
- privilege assignments for built-in or extension-created objects,
- such changes were formerly lost in a dump and reload. Now,
-
pg_dump recognizes and dumps such changes.+ While it has always been possible for a superuser to change
+ the privilege assignments for built-in or extension-created
+ objects, such changes were formerly lost in a dump and reload.
+
Now, pg_dump recognizes and dumps such changes. (This works only when dumping from a 9.6 or later server, however.)
2016-04-06 [3b3fcc4ee] pg_dump: Add table qualifications to some tags
-->
- In
pg_dump, include the table name in object tags- for object types that are only uniquely named per-table (for
- example, triggers) (Peter Eisentraut)
-
-
-
-
-
- Improve
pg_restore's switch to- match all types of relations, not only plain tables (Craig Ringer)
+ In
pg_dump, include the table name in object+ tags for object types that are only uniquely named per-table
+ (for example, triggers) (Peter Eisentraut)
- Support multiple and
- command-line options (Pavel Stehule, Catalin Iacob)
-
-
- To allow this with sane behavior, one backwards incompatibility had to
- be introduced: no longer
- implies .
-
-
-
-
-
- Add a \crosstabview command that prints the
- results of a query in a cross-tabulated display
- (Daniel Vérité)
+ Add a \crosstabview command that prints the results of
+ a query in a cross-tabulated display (Daniel Vérité)
- In the crosstab display, data values from one query result column are
- placed in a grid whose column and row headers come from other query
- result columns.
+ In the crosstab display, data values from one query result column
+ are placed in a grid whose column and row headers come from other
+ query result columns.
- This is very handy after getting an unexpected error — you no
- longer need to adjust the VERBOSITY variable and recreate
- the failure in order to see error fields that aren't shown by
- default.
+ This is useful after getting an unexpected error — you
+ no longer need to adjust the VERBOSITY variable and
+ recreate the failure in order to see error fields that are not
+ shown by default.
2016-05-06 [9b66aa006] Fix psql's \ev and \sv commands so that they handle view
-->
- Add \ev and \sv commands
- for editing and showing view definitions (Petr Korobeinikov)
+ Add \ev and \sv commands for editing and
+ showing view definitions (Petr Korobeinikov)
- These are parallel to the existing \ef and \sf
- commands for functions.
+ These are parallel to the existing \ef and
+ \sf commands for functions.
2016-04-04 [2bbe9112a] Add a \gexec command to psql for evaluation of computed
-->
- Add a \gexec command that executes a query and re-submits
- the result(s) as new queries (Corey Huinker)
+ Add a \gexec command that executes a query and
+ re-submits the result(s) as new queries (Corey Huinker)
2015-10-05 [2145a7660] psql: allow \pset C in setting the title, matches \C
-->
- Allow \pset C string to set the
- table title, for consistency
- with \C string (Bruce Momjian)
+ Allow \pset C string
+ to set the table title, for consistency with \C
+ string (Bruce Momjian)
2016-03-11 [69ab7b9d6] psql: Don't automatically use expanded format when there
-->
- In \pset expanded auto mode, do not use expanded format
- for query results with only one column (Andreas Karlsson, Robert Haas)
+ In \pset expanded auto mode, do not use expanded
+ format for query results with only one column (Andreas Karlsson,
+ Robert Haas)
2016-06-15 [9901d8ac2] Use strftime("%c") to format timestamps in psql's \watch
-->
- Improve the headers output by the \watch command
+ Improve the headers output of the \watch command
(Michael Paquier, Tom Lane)
- Include the \pset title string if one has been set, and
- shorten the prefabricated part of the header to be
- timestamp (every Ns).
- Also, the timestamp format now obeys
psql's locale- environment.
+ Include the \pset title string if one has
+ been set, and shorten the prefabricated part of the
+ header to be timestamp (every
+ Ns). Also, the timestamp format now
+
obeys psql's locale environment.
2015-12-20 [d854118c8] Teach psql's tab completion to consider the entire input
-->
- Improve tab-completion logic to consider the
- entire input query, not only the current line (Tom Lane)
+ Improve tab-completion logic to consider the entire input query,
+ not only the current line (Tom Lane)
- Previously, breaking a command into multiple lines defeated any tab
- completion rules that would have needed to see words on earlier lines.
+ Previously, breaking a command into multiple lines defeated any
+ tab completion rules that needed to see words on earlier lines.
Numerous minor improvements in tab-completion behavior (Peter
Eisentraut, Vik Fearing, Kevin Grittner, Kyotaro Horiguchi, Jeff
- Janes, Andreas Karlsson, Fujii Masao, Thomas Munro, Masahiko Sawada,
- Pavel Stehule)
+ Janes, Andreas Karlsson, Fujii Masao, Thomas Munro, Masahiko
+ Sawada, Pavel Stehule)
2015-07-07 [275f05c99] Add psql PROMPT variable showing the pid of the connecte
-->
- Add a PROMPT option %p to
- insert the process ID of the connected backend (Julien Rouhaud)
+ Add a PROMPT option %p to insert the
+ process ID of the connected backend (Julien Rouhaud)
This commit is also listed under libpq and PL/pgSQL
-->
- Introduce a feature whereby the CONTEXT field of messages
- can be suppressed, either always or only for non-error messages
- (Pavel Stehule)
+ Introduce a feature whereby the CONTEXT field of
+ messages can be suppressed, either always or only for non-error
+ messages (Pavel Stehule)
- This change allows SQL commands in scripts to span multiple lines.
- Existing custom scripts will need to be modified to add a semicolon
- at the end of each line that does not have one already. (Doing so
- does not break the script for use with older versions
+ This change allows SQL commands in scripts to span multiple
+ lines. Existing custom scripts will need to be modified to add a
+ semicolon at the end of each line that does not have one already.
+ (Doing so does not break the script for use with older versions
2016-05-06 [951529948] Improve handling of numeric-valued variables in pgbench.
-->
- Support floating-point arithmetic, as well as
- some built-in functions,
- in expressions in backslash commands (Fabien Coelho)
+ Support floating-point arithmetic, as well as some
+ linkend="pgbench-builtin-functions">built-in functions, in
+ expressions in backslash commands (Fabien Coelho)
2016-03-29 [ad9566470] pgbench: Remove \setrandom.
-->
- Replace \setrandom with built-in functions (Fabien Coelho)
+ Replace \setrandom with built-in functions (Fabien
+ Coelho)
- The new built-in functions include random(),
- random_exponential(), and random_gaussian(),
- which perform the same work as \setrandom, but are easier
- to use since they can be embedded in larger expressions. Since these
- additions have made \setrandom obsolete, remove it.
+ The new built-in functions include
+ linkend="pgbench-functions">random(),
+ random_exponential(), and
+ random_gaussian(), which perform the same work as
+ \setrandom, but are easier to use since they can be
+ embedded in larger expressions. Since these additions have made
+ \setrandom obsolete, remove it.
2016-03-03 [d561f1cae] pgbench: accept unambiguous builtin prefixes for -b
-->
- Allow invocation of multiple copies of the built-in scripts, not only
- custom scripts (Fabien Coelho)
+ Allow invocation of multiple copies of the built-in scripts,
+ not only custom scripts (Fabien Coelho)
- This is done with the new
- to
+ This is done with the new
+ similarly to
2016-02-01 [1d0c3b3f8] pgbench: allow per-script statistics
-->
- Collect statistics for each script in a multi-script run
- (Fabien Coelho)
+ Collect statistics for each script in a multi-script run (Fabien
+ Coelho)
- This feature adds an intermediate level of detail to existing global
- and per-command statistics printouts.
+ This feature adds an intermediate level of detail to existing
+ global and per-command statistics printouts.
2015-09-16 [1def9063c] pgbench progress with timestamp
-->
- Add a
- Unix epoch timestamps, instead of time since the run started
+ Add a
+ with Unix epoch timestamps, instead of time since the run started
(Fabien Coelho)
2015-07-03 [ba3deeefb] Lift the limitation that # of clients must be a multiple
-->
- Allow the number of client connections (
- exact multiple of the number of threads (
+ Allow the number of client connections (
+ be an exact multiple of the number of threads (
(Fabien Coelho)
2016-03-09 [accf7616f] pgbench: When -T is used, don't wait for transactions be
-->
- When the
- the specified time (Fabien Coelho)
+ When the
+ of the specified time (Fabien Coelho)
- Previously, specifying a low transaction rate could
- cause
pgbench to wait significantly longer than that.+ Previously, specifying a low transaction rate could cause
+
pgbench to wait significantly longer than+ specified.
2015-12-17 [66d947b9d] Adjust behavior of single-user -j mode for better initdb
-->
- Improve error reporting during
initdb's post-bootstrap- phase (Tom Lane)
+ Improve error reporting during
initdb's+ post-bootstrap phase (Tom Lane)
- Previously, an error here led to reporting the entire input file as
- the failing query; now just the current query is reported.
- To get the desired behavior, queries in
initdb's- input files must be separated by blank lines.
+ Previously, an error here led to reporting the entire input
+ file as the failing query; now just the current
+ query is reported. To get the desired behavior, queries in
+
initdb's input files must be separated by blank+ lines.
2015-12-17 [c4a8812cf] Use just one standalone-backend session for initdb's pos
-->
- Speed up
initdb by using just one standalone-backend- session for all the post-bootstrap steps (Tom Lane)
+ Speed up
initdb by using just one+ standalone-backend session for all the post-bootstrap steps
+ (Tom Lane)
2015-07-02 [726117243] Remove obsolete heap_formtuple/modifytuple/deformtuple f
-->
- Remove obsolete heap_formtuple/heap_modifytuple/heap_deformtuple
+ Remove obsolete
+ heap_formtuple/heap_modifytuple/heap_deformtuple
functions (Peter Geoghegan)
- This may result in warnings and/or wasted code space with very old
- compilers, but the notational improvement seems worth it.
+ This may result in warnings and/or wasted code space with very
+ old compilers, but the notational improvement seems worth it.
2016-05-06 [6bd356c33] Add TAP tests for pg_dump
-->
- Improve TAP testing infrastructure
- (Michael Paquier, Craig Ringer, Álvaro Herrera, Stephen Frost)
+ Improve
TAP testing infrastructure (Michael+ Paquier, Craig Ringer, Álvaro Herrera, Stephen Frost)
- Notably, it is now possible to test recovery scenarios using this
- infrastructure.
+ Notably, it is now possible to test recovery scenarios using
+ this infrastructure.
- Tab-completion rules are now considerably easier to write, and more
- compact.
+ Tab-completion rules are now considerably easier to write, and
+ more compact.
- The core code doesn't use this catalog for authentication, but
- extensions might wish to consult it.
+ The core code does not use this catalog for authentication,
+ but extensions might wish to consult it.
2016-01-21 [be44ed27b] Improve index AMs' opclass validation procedures.
-->
- Restructure index access method API to hide most of it at the C level
- (Alexander Korotkov)
+ Restructure index access method
API to hide most of+
it at the C level (Alexander Korotkov)
- This change modernizes the index AM API to look more like the designs
- we've adopted for foreign data wrappers and tablesample handlers.
- This simplifies the C code and should make it more feasible to define
- index access methods in installable extensions. A consequence is
- that most of the columns of the pg_am system catalog
- have disappeared.
+ This change modernizes the index
AM API to look more+ like the designs we have adopted for foreign data wrappers and
+
tablesample handlers. This simplifies the C code
+ and should make it more feasible to define index access methods in
+ installable extensions. A consequence is that most of the columns
+ of the pg_am system catalog have disappeared.
This infrastructure allows
pg_dump to dump changes- that an installation may have made in privileges attached to system
- objects. Formerly, such changes would be lost in a dump and reload,
- but now they can be preserved.
+ that an installation may have made in privileges attached to
+ system objects. Formerly, such changes would be lost in a dump
+ and reload, but now they can be preserved.
2016-02-04 [c1772ad92] Change the way that LWLocks for extensions are allocated
-->
- Change the way that extensions allocate custom LWLocks
+ Change the way that extensions allocate custom LWLocks
(Amit Kapila, Robert Haas)
- The RequestAddinLWLocks() function is removed, and
- replaced by RequestNamedLWLockTranche(). This allows
- better identification of custom LWLocks, and is less error-prone.
+ The RequestAddinLWLocks() function is removed,
+ and replaced by RequestNamedLWLockTranche().
+ This allows better identification of custom LWLocks,
+ and is less error-prone.
- This change allows FDWs or custom scan providers to store data in a
- plan tree in a more convenient format than was previously possible.
+ This change allows
FDWs or custom scan providers+ to store data in a plan tree in a more convenient format than
+ was previously possible.
-->
Make the planner deal with post-scan/join query steps by generating
- and comparing Paths, replacing a lot of very ad-hoc logic (Tom Lane)
+ and comparing Paths, replacing a lot of ad-hoc logic
+ (Tom Lane)
This change provides only marginal user-visible improvements today,
but it enables future work on a lot of upper-planner improvements
- that were impractical to tackle in the old code structure.
+ that were impractical to tackle using the old code structure.
This change allows the computation of an aggregate function to be
split into separate parts, for example so that parallel worker
- processes can cooperate on computing an aggregate. In future it
- might allow aggregation across local and remote data to occur
+ processes can cooperate on computing an aggregate. In future
+ it might allow aggregation across local and remote data to occur
partially on the remote end.
2016-03-24 [c1156411a] Move psql's psqlscan.l into src/fe_utils.
-->
- Separate out
psql's flex lexer to make it usable by- other client programs too (Tom Lane, Kyotaro Horiguchi)
+ Separate out
psql's flex lexer to+ make it usable by other client programs too (Tom Lane, Kyotaro
+ Horiguchi)
This eliminates code duplication for programs that need to be able
to parse SQL commands well enough to identify command boundaries.
- Doing that in full generality is more painful than one could wish,
- and up to now only
psql has really gotten it right- among our supported client programs.
+ Doing that in full generality is more painful than one could
+ wish, and up to now only
psql has really gotten+ it right among our supported client programs.
- A new source-code subdirectory src/fe_utils/ has been
- created to hold this and other code that's shared across our client
- programs. Formerly such sharing was accomplished by symlinking or
- copying source files at build time, which was ugly and required
- duplicate compilation work.
+ A new source-code subdirectory src/fe_utils/ has
+ been created to hold this and other code that is shared across
+ our client programs. Formerly such sharing was accomplished by
+ symbolic linking or copying source files at build time, which
+ was ugly and required duplicate compilation.
2016-03-21 [98a64d0bd] Introduce WaitEventSet API.
-->
- Introduce WaitEventSet API to allow efficient waiting for event
- sets that usually don't change from one wait to the next
- (Andres Freund, Amit Kapila)
+ Introduce
WaitEventSet API to allow+ efficient waiting for event sets that usually do not change from
+ one wait to the next (Andres Freund, Amit Kapila)
2016-04-01 [65578341a] Add Generic WAL interface
-->
- Add a generic interface for writing WAL records
+ Add a generic interface for writing
WAL records
(Alexander Korotkov, Petr Jelínek, Markus Nullmeier)
- This change allows extensions to write WAL records for changes to
- pages with standard layout. The problem of needing to replay WAL
- without access to the extension is solved by having generic replay
- code. This allows extensions to implement, for example, index access
- methods and have WAL support for them.
+ This change allows extensions to write
WAL records for+ changes to pages with standard layout. The problem of needing to
+ replay
WAL without access to the extension is solved by+ having generic replay code. This allows extensions to implement,
+ for example, index access methods and have
WAL+ support for them.
2016-04-06 [3fe3511d0] Generic Messages for Logical Decoding
-->
- Support generic WAL messages for logical decoding
+ Support generic
WAL messages for logical decoding
(Petr Jelínek, Andres Freund)
- This feature allows extensions to insert data into the WAL stream
- that can be read by logical-decoding plugins, but is not connected to
- physical data restoration.
+ This feature allows extensions to insert data into the
+
WAL stream that can be read by logical-decoding+ plugins, but is not connected to physical data restoration.
2016-03-30 [87545f541] Use traversalValue in SP-GiST range opclass.
-->
- Allow SP-GiST operator classes to store an arbitrary traversal
- value while descending the index (Alexander Lebedev, Teodor Sigaev)
+ Allow SP-GiST operator classes to store an arbitrary
+ traversal value while descending the index (Alexander
+ Lebedev, Teodor Sigaev)
- This is somewhat like the reconstructed value, but it could
- be any arbitrary chunk of data, it need not be of the same data type
- as the indexed column.
+ This is somewhat like the reconstructed value, but it
+ could be any arbitrary chunk of data, it need not be of the same
+ data type as the indexed column.
2016-04-04 [66229ac00] Introduce a LOG_SERVER_ONLY ereport level, which is neve
-->
- Introduce a LOG_SERVER_ONLY message level
- for ereport() (David Steele)
+ Introduce a LOG_SERVER_ONLY message level for
+ ereport() (David Steele)
- This level acts like LOG except that the message is never
- sent to the client. It's meant for use in auditing and similar
- applications.
+ This level acts like LOG except that the message is
+ never sent to the client. It is meant for use in auditing and
+ similar applications.
2016-07-01 [548af97fc] Provide and use a makefile target to build all generated
-->
- Provide a makefile target to build all generated headers (Michael
- Paquier, Tom Lane)
+ Provide a Makefile target to build all generated
+ headers (Michael Paquier, Tom Lane)
submake-generated-headers can now be invoked to ensure
- that generated backend header files are up-to-date. This is useful in
- subdirectories that might be built standalone.
+ that generated backend header files are up-to-date. This is
+ useful in subdirectories that might be built standalone.
2016-04-01 [9ee014fc8] Bloom index contrib module
-->
- Add contrib/bloom module that implements an index access
- method based on Bloom filtering (Teodor Sigaev, Alexander Korotkov)
+ Add contrib/bloom module that implements an index
+ access method based on Bloom filtering (Teodor Sigaev, Alexander
+ Korotkov)
2015-12-28 [81ee726d8] Code and docs review for cube kNN support.
-->
- In contrib/cube, introduce distance operators for cubes,
- and support kNN-style searches in GiST indexes on cube columns
- (Stas Kelvich)
+ In contrib/cube, introduce distance operators for
+ cubes, and support kNN-style searches in GiST indexes on cube
+ columns (Stas Kelvich)
2016-02-03 [41d2c081c] Make hstore_to_jsonb_loose match hstore_to_json_loose on
-->
- Make contrib/hstore's hstore_to_jsonb_loose()
- and hstore_to_json_loose() functions agree on what's a
- number (Tom Lane)
+ Make
contrib/hstore's
+ linkend="hstore-func-table">hstore_to_jsonb_loose()
+ and hstore_to_json_loose() functions agree on what
+ is a number (Tom Lane)
Previously, hstore_to_jsonb_loose() would convert
- numeric-looking strings to JSON numbers, rather than strings, even if
- they did not exactly match the JSON syntax specification for numbers.
- This was inconsistent with hstore_to_json_loose(), so
- tighten the test to match the JSON syntax.
+ numeric-looking strings to
JSON numbers, rather than+ strings, even if they did not exactly match the
JSON+ syntax specification for numbers. This was inconsistent with
+ hstore_to_json_loose(), so tighten the test to match
2015-07-21 [c6fbe6d6f] Add selectivity estimation functions for intarray operat
-->
- Add selectivity estimation functions for contrib/intarray
- operators, to improve plans for queries using those operators (Yury
- Zhuravlev, Alexander Korotkov)
+ Add selectivity estimation functions for
+ contrib/intarray operators, to improve plans for
+ queries using those operators (Yury Zhuravlev, Alexander Korotkov)
2015-11-25 [d6061f83a] Improve pageinspect module
-->
- Make contrib/pageinspect's heap_page_items()
- function show the raw data in each tuple, and add new
- functions tuple_data_split()
- and heap_page_item_attrs() for inspection of individual
+ Make
+ linkend="pageinspect">contrib/pageinspect's
+ heap_page_items() function show the raw data in each
+ tuple, and add new functions tuple_data_split() and
+ heap_page_item_attrs() for inspection of individual
tuple fields (Nikolay Shaplov)
2016-03-09 [188f359d3] pgcrypto: support changing S2K iteration count
-->
- Add an optional S2K iteration count parameter
- to contrib/pgcrypto's pgp_sym_encrypt()
- function (Jeff Janes)
+ Add an optional S2K iteration count parameter to
+ contrib/pgcrypto's
+ pgp_sym_encrypt() function (Jeff Janes)
2016-03-16 [f576b17cd] Add word_similarity to pg_trgm contrib module.
-->
- Add support for word similarity
- to contrib/pg_trgm
- (Alexander Korotkov, Artur Zakirov)
+ Add support for word similarity to
+ contrib/pg_trgm (Alexander Korotkov, Artur Zakirov)
2016-06-20 [9c852566a] Fix comparison of similarity to threshold in GIST trigra
-->
- Add configuration parameter pg_trgm.similarity_threshold
- for contrib/pg_trgm's similarity threshold
- (Artur Zakirov)
+ Add configuration parameter
+
pg_trgm.similarity_threshold for
+ linkend="pgtrgm">contrib/pg_trgm's similarity
+ threshold (Artur Zakirov)
2015-07-20 [97f301464] This supports the triconsistent function for pg_trgm GIN
-->
- Improve contrib/pg_trgm's GIN operator class to speed up
- index searches in which both common and rare keys appear (Jeff Janes)
+ Improve contrib/pg_trgm's GIN operator class to
+ speed up index searches in which both common and rare keys appear
+ (Jeff Janes)
2015-09-07 [49124613f] contrib/sslinfo: add ssl_extension_info SRF
-->
- Add ssl_extension_info() function
- to contrib/sslinfo, to print information about SSL
- extensions present in the X509 certificate used for the current
- connection (Dmitry Voronin)
-
-
-
-
-
- Extend contrib/unaccent's
- standard unaccent.rules file to handle all diacritics
- known to Unicode, and expand ligatures correctly
- (Thomas Munro, Léonard Benedetti)
-
-
- The previous version omitted some less-common letters with diacritic
- marks. It now also expands ligatures into separate letters.
- Installations that use this rules file may wish to
- rebuild tsvector columns and indexes that depend on the
- result.
+ Add ssl_extension_info()
+ function to contrib/sslinfo, to print information
+ about
SSL extensions present in the X509+ certificate used for the current connection (Dmitry Voronin)
- Users can enable this feature when the extension is known to exist in
- a compatible version in the remote database. It allows more efficient
- execution of queries involving extension operators.
+ Users can enable this feature when the extension is known to exist
+ in a compatible version in the remote database. It allows more
+ efficient execution of queries involving extension operators.
Formerly, this involved sending a SELECT FOR UPDATE
command and then updating or deleting the selected rows one-by-one.
- While that's still necessary if the operation requires any local
- processing, it can now be done remotely if all elements of the query
- are safe to send to the remote server.
+ While that is still necessary if the operation requires any local
+ processing, it can now be done remotely if all elements of the
+ query are safe to send to the remote server.
- Formerly, postgres_fdw always fetched 100 rows at a time
- from remote queries; now that behavior is adjustable.
+ Formerly, postgres_fdw always fetched 100 rows at
+ a time from remote queries; now that behavior is configurable.
2016-01-28 [96198d94c] Avoid multiple foreign server connections when all use s
-->
- Use a single foreign-server connection for local user IDs that all
- map to the same remote user (Ashutosh Bapat)
+ Use a single foreign-server connection for local user IDs that
+ all map to the same remote user (Ashutosh Bapat)
- Previously, a local query cancellation request did nothing to cause
- an already-sent remote query to terminate early.
+ Previously, a local query cancellation request did not cause an
+ already-sent remote query to terminate early.
projects / postgresql.git / commitdiff