On Wed, Jan 29, 2014 at 08:51:26PM +, Andrew Dunstan wrote:
> Add json_array_elements_text function.
>
> This was a notable omission from the json functions added in 9.3 and
> there have been numerous complaints about its absence.
>
> Laurence Rowe.
The docs seem to have bug:
it says that t
Fix documented return type of json_array_elements_text.
Per gripe from hubert depesz lubaczewski.
Also improve examples for this and json_array_elements so they match the
example results.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e9afdf2f4bddb9d3a5a09aa8eff7fc
entab: add new options
Add new entab options to process only C comment whitespace after
periods, and to protect leading whitespace.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5ff47acf8f2da1103219a99e61b4862dba8b6f3d
Modified Files
--
src/tools/enta
Add tab completion for ALTER TABLESPACE MOVE in psql.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a87ae38be844a140786bf2fb3f3f8a094d51fa26
Modified Files
--
src/bin/psql/tab-complete.c | 30 ++
1 file changed, 26 insertion
pgindent: add --list-of-typedefs option
Allows typedefs to be specified on the command line, per request from
Andrew.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/cad1e022b265be8f2526cd82e5d2f8da3ba9f613
Modified Files
--
src/tools/pgindent/pgindent
pgindent: add Perl comment
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/290d2cb500ea8903cf605e626fc46ea11a619f28
Modified Files
--
src/tools/pgindent/pgindent |2 ++
1 file changed, 2 insertions(+)
--
Sent via pgsql-committers mailing list (pgsq
system catalogs: reorder pg_amproc entries into proper sections
Report form Antonin Houska
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/fc4ffba9685809474a1cb9aa7bd122f62f0ee2e5
Modified Files
--
src/include/catalog/pg_amproc.h | 52
docs: specify FOR UPDATE/SHARE incompatibilities
Document that FOR UPDATE/SHARE are incompatible with GROUP BY, DISTINCT,
HAVING and window functions.
Michael Paquier
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8824b38909b28c801456ade7a63ff67e3795ed1d
Modified
doc: authentication wording improvements
Suggested by David Tonhofer
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/384fbd1a5d49c3acaecf15d7a7eefae49049f6eb
Modified Files
--
doc/src/sgml/client-auth.sgml |4 ++--
1 file changed, 2 insertions(+), 2 d
Add some examples to the postgres_fdw documentation.
Michael Paquier
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e93ca1618b92ff4ca3e1ed3bff89179d3e2abd9e
Modified Files
--
doc/src/sgml/postgres-fdw.sgml | 62
docs: mention tgconstrindid supports exclusion constraints
Dean Rasheed
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3fd3e34914a2aa520a8bc5109a773621385cf1f4
Modified Files
--
doc/src/sgml/catalogs.sgml |3 ++-
1 file changed, 2 insertions(+), 1 d
Disallow use of SSL v3 protocol in the server as well as in libpq.
Commit 820f08cabdcbb8998050c3d4873e9619d6d8cba4 claimed to make the server
and libpq handle SSL protocol versions identically, but actually the server
was still accepting SSL v3 protocol while libpq wasn't. Per discussion,
SSL v3
doc: mention data page checksums in WAL section
Backpatch to 9.3
Adjusted patch from Ian Lawrence Barwick
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/85317e88ccae270ef77bd01c2d3d55a900df2d72
Modified Files
--
doc/src/sgml/wal.sgml |7 ---
1 f
doc: mention data page checksums in WAL section
Backpatch to 9.3
Adjusted patch from Ian Lawrence Barwick
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/5dc6cab2d2b92bb066291a28d856d37d53e3a944
Modified Files
--
doc/src/sgml/wal.sgml |7
chkpass: check for NULL return value from crypt()
Report from Jozef Mlich using Coverity
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/6afe200ceea818c82e3a1a754c5043e7df1efa10
Modified Files
--
contrib/chkpass/chkpass.c |9 -
1 file changed
doc: mention statistics reset during crash recovery
Takayuki Tsunakawa
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/637fab6e575b36d3a4368e7c2b923231c5504035
Modified Files
--
doc/src/sgml/monitoring.sgml |6 --
1 file changed, 4 insertions(+),
Clear MyProc and MyProcSignalState before they become invalid.
Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped. Although processes
using the new dynamic
Clear MyProc and MyProcSignalState before they become invalid.
Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped. Although processes
using the new dynamic
Clear MyProc and MyProcSignalState before they become invalid.
Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped. Although processes
using the new dynamic
Clear MyProc and MyProcSignalState before they become invalid.
Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped. Although processes
using the new dynamic
Clear MyProc and MyProcSignalState before they become invalid.
Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped. Although processes
using the new dynamic
Clear MyProc and MyProcSignalState before they become invalid.
Evidence from buildfarm member crake suggests that the new test_shm_mq
module is routinely crashing the server due to the arrival of a SIGUSR1
after the shared memory segment has been unmapped. Although processes
using the new dynamic
pg_restore: make help output plural for multi-enabled options
per report from Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5168c76964fe90646b69b37e2c5bc7b60ba12d65
Modified Files
--
src/bin/pg_dump/pg_restore.c | 12 ++--
1
docs: mention 'g' is not in the regex embedded options table
Mentioned in substring() and regexp_replace() sections.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5bdef38b8917cfbe206d14969c61a5d38fc822b6
Modified Files
--
doc/src/sgml/func.sgml |8
Introduce replication slots.
Replication slots are a crash-safe data structure which can be created
on either a master or a standby to prevent premature removal of
write-ahead log segments needed by a standby, as well as (with
hot_standby_feedback=on) pruning of tuples whose removal would cause
re
On Sat, Feb 1, 2014 at 12:50 PM, Robert Haas wrote:
> Introduce replication slots.
>
> Replication slots are a crash-safe data structure which can be created
> on either a master or a standby to prevent premature removal of
> write-ahead log segments needed by a standby, as well as (with
> hot_sta
26 matches
Mail list logo
