[COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.
Allow multiple hostaddrs to go with multiple hostnames. Also fix two other issues, while we're at it: * In error message on connection failure, if multiple network addresses were given as the host option, as in "host=127.0.0.1,127.0.0.2", the error message printed the address twice. * If there were many more ports than hostnames, the error message would always claim that there was one port too many, even if there was more than one. For example, if you gave 2 hostnames and 5 ports, the error message claimed that you gave 2 hostnames and 3 ports. Discussion: https://www.postgresql.org/message-id/10badbc6-4d5a-a769-623a-f7ada43e1...@iki.fi Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7b02ba62e9ffad5b14c24756a0c2aeae839c9d05 Modified Files -- doc/src/sgml/libpq.sgml | 55 +++- src/interfaces/libpq/fe-connect.c | 258 -- src/interfaces/libpq/libpq-int.h | 3 +- 3 files changed, 219 insertions(+), 97 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.
On Mon, Jul 10, 2017 at 6:30 PM, Heikki Linnakangas wrote: > Allow multiple hostaddrs to go with multiple hostnames. > > Also fix two other issues, while we're at it: > > * In error message on connection failure, if multiple network addresses > were given as the host option, as in "host=127.0.0.1,127.0.0.2", the > error message printed the address twice. > > * If there were many more ports than hostnames, the error message would > always claim that there was one port too many, even if there was more than > one. For example, if you gave 2 hostnames and 5 ports, the error message > claimed that you gave 2 hostnames and 3 ports. > > Discussion: > https://www.postgresql.org/message-id/10badbc6-4d5a-a769-623a-f7ada43e1...@iki.fi > > Branch > -- > master > > Details > --- > https://git.postgresql.org/pg/commitdiff/7b02ba62e9ffad5b14c24756a0c2aeae839c9d05 > > Modified Files > -- > doc/src/sgml/libpq.sgml | 55 +++- > src/interfaces/libpq/fe-connect.c | 258 -- > src/interfaces/libpq/libpq-int.h | 3 +- > 3 files changed, 219 insertions(+), 97 deletions(-) > > > -- > Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-committers Hi, This commit seems be cause of the documentation compilation error. I think is missing. $ make -C doc/src/sgml/ make: Entering directory `/home/masahiko/pgsql/source/postgresql/doc/src/sgml' osx -wall -wno-unused-param -wno-empty -wfully-tagged -D . -D . -x lower postgres.sgml >postgres.xml.tmp osx:libpq.sgml:926:9:E: end tag for "SECT3" omitted, but OMITTAG NO was specified osx:libpq.sgml:891:3: start tag was here make: *** [postgres.xml] Error 1 make: Leaving directory `/home/masahiko/pgsql/source/postgresql/doc/src/sgml' Attached small patch fixes this. Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 124c21b..98b6938 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -923,6 +923,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname host, it is not possible to e.g. specify a different username for different hosts. + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix COPY's handling of transition tables with indexes.
Fix COPY's handling of transition tables with indexes. Commit c46c0e5202e8cfe750c6629db7852fdb15d528f3 failed to pass the TransitionCaptureState object to ExecARInsertTriggers() in the case where it's using heap_multi_insert and there are indexes. Repair. Thomas Munro, from a report by David Fetter Discussion: https://postgr.es/m/20170708084213.GA14720%40fetter.org Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/1add0b15f117769f619af12720bea2f73d4f7359 Modified Files -- src/backend/commands/copy.c| 2 +- src/test/regress/expected/triggers.out | 7 ++- src/test/regress/sql/triggers.sql | 7 +++ 3 files changed, 14 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix check for empty hostname.
Fix check for empty hostname. As reported by Arthur Zakirov, Gcc 7.1 complained about this with -Wpointer-compare. Discussion: https://www.postgresql.org/message-id/CAKNkYnybV_NFVacGbW=vspzao3twrjfni+9ibob66yqqmzo...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4d06f1f858d0fea01a2cde74d8b831a823776355 Modified Files -- src/interfaces/libpq/fe-connect.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix missing tag in the docs.
Fix missing tag in the docs. Masahiko Sawada Discussion: https://www.postgresql.org/message-id/CAD21AoBCwcTNMdrVWq8T0hoOs2mWSYq9PRJ_fr6SH8HdO+m=0...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d137a6dc239bd32b424826acbb25277ac611ddb1 Modified Files -- doc/src/sgml/libpq.sgml | 1 + 1 file changed, 1 insertion(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.
On 07/10/2017 01:27 PM, Masahiko Sawada wrote: This commit seems be cause of the documentation compilation error. I think is missing. ... Attached small patch fixes this. Thanks, committed! Strangely, it worked on my system, despite that clear mistake. Looks like the 'osx' tool is more strict than what I had installed. I have now also installed opensp, so won't make this mistake again. - Heikki -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared
On Windows, retry process creation if we fail to reserve shared memory. We've heard occasional reports of backend launch failing because pgwin32_ReserveSharedMemoryRegion() fails, indicating that something has already used that address space in the child process. It's not very clear what, given that we disable ASLR in Windows builds, but suspicion falls on antivirus products. It'd be better if we didn't have to disable ASLR, anyway. So let's try to ameliorate the problem by retrying the process launch after such a failure, up to 100 times. Patch by me, based on previous work by Amit Kapila and others. This is a longstanding issue, so back-patch to all supported branches. Discussion: https://postgr.es/m/caa4ek1+r6hsx6t_yvwtx+nrznevp+mrqxadgjzchcau8uij...@mail.gmail.com Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/59892b1209b9202338dbfc65c9a59cbed182befb Modified Files -- src/backend/postmaster/postmaster.c | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared
On Windows, retry process creation if we fail to reserve shared memory. We've heard occasional reports of backend launch failing because pgwin32_ReserveSharedMemoryRegion() fails, indicating that something has already used that address space in the child process. It's not very clear what, given that we disable ASLR in Windows builds, but suspicion falls on antivirus products. It'd be better if we didn't have to disable ASLR, anyway. So let's try to ameliorate the problem by retrying the process launch after such a failure, up to 100 times. Patch by me, based on previous work by Amit Kapila and others. This is a longstanding issue, so back-patch to all supported branches. Discussion: https://postgr.es/m/caa4ek1+r6hsx6t_yvwtx+nrznevp+mrqxadgjzchcau8uij...@mail.gmail.com Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c0077f7383e3a9cd36d566fd8f6f4eb9fd55e0e6 Modified Files -- src/backend/postmaster/postmaster.c | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared
On Windows, retry process creation if we fail to reserve shared memory. We've heard occasional reports of backend launch failing because pgwin32_ReserveSharedMemoryRegion() fails, indicating that something has already used that address space in the child process. It's not very clear what, given that we disable ASLR in Windows builds, but suspicion falls on antivirus products. It'd be better if we didn't have to disable ASLR, anyway. So let's try to ameliorate the problem by retrying the process launch after such a failure, up to 100 times. Patch by me, based on previous work by Amit Kapila and others. This is a longstanding issue, so back-patch to all supported branches. Discussion: https://postgr.es/m/caa4ek1+r6hsx6t_yvwtx+nrznevp+mrqxadgjzchcau8uij...@mail.gmail.com Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/bc0f76e7ad3704cc5ed3caf7923ef0d94c2b69b1 Modified Files -- src/backend/postmaster/postmaster.c | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared
On Windows, retry process creation if we fail to reserve shared memory. We've heard occasional reports of backend launch failing because pgwin32_ReserveSharedMemoryRegion() fails, indicating that something has already used that address space in the child process. It's not very clear what, given that we disable ASLR in Windows builds, but suspicion falls on antivirus products. It'd be better if we didn't have to disable ASLR, anyway. So let's try to ameliorate the problem by retrying the process launch after such a failure, up to 100 times. Patch by me, based on previous work by Amit Kapila and others. This is a longstanding issue, so back-patch to all supported branches. Discussion: https://postgr.es/m/caa4ek1+r6hsx6t_yvwtx+nrznevp+mrqxadgjzchcau8uij...@mail.gmail.com Branch -- REL9_2_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a4a590ee7913eb60e1832d64e73a81b394dd542c Modified Files -- src/backend/postmaster/postmaster.c | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared
On Windows, retry process creation if we fail to reserve shared memory. We've heard occasional reports of backend launch failing because pgwin32_ReserveSharedMemoryRegion() fails, indicating that something has already used that address space in the child process. It's not very clear what, given that we disable ASLR in Windows builds, but suspicion falls on antivirus products. It'd be better if we didn't have to disable ASLR, anyway. So let's try to ameliorate the problem by retrying the process launch after such a failure, up to 100 times. Patch by me, based on previous work by Amit Kapila and others. This is a longstanding issue, so back-patch to all supported branches. Discussion: https://postgr.es/m/caa4ek1+r6hsx6t_yvwtx+nrznevp+mrqxadgjzchcau8uij...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/45e004fb4e3937dbdabf6d5c1706f1a02fdceb94 Modified Files -- src/backend/postmaster/postmaster.c | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared
On Windows, retry process creation if we fail to reserve shared memory. We've heard occasional reports of backend launch failing because pgwin32_ReserveSharedMemoryRegion() fails, indicating that something has already used that address space in the child process. It's not very clear what, given that we disable ASLR in Windows builds, but suspicion falls on antivirus products. It'd be better if we didn't have to disable ASLR, anyway. So let's try to ameliorate the problem by retrying the process launch after such a failure, up to 100 times. Patch by me, based on previous work by Amit Kapila and others. This is a longstanding issue, so back-patch to all supported branches. Discussion: https://postgr.es/m/caa4ek1+r6hsx6t_yvwtx+nrznevp+mrqxadgjzchcau8uij...@mail.gmail.com Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/afd1415a4426bb9962d8dff605f11df415b58fdc Modified Files -- src/backend/postmaster/postmaster.c | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Translation updates
Translation updates Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: c5a8de3653bb1af6b0eb41cc6bf090c5522df52b Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6c774caf0ea6977f00af4225192915f0a602ea3d Modified Files -- src/backend/po/es.po | 15919 +++-- src/backend/po/it.po | 13288 +++ src/bin/initdb/po/es.po | 499 +- src/bin/initdb/po/fr.po | 522 +- src/bin/initdb/po/it.po | 412 +- src/bin/pg_archivecleanup/nls.mk | 2 +- src/bin/pg_archivecleanup/po/es.po | 175 + src/bin/pg_archivecleanup/po/fr.po | 174 + src/bin/pg_basebackup/po/es.po | 758 +- src/bin/pg_basebackup/po/fr.po | 1142 ++- src/bin/pg_basebackup/po/it.po | 728 +- src/bin/pg_config/po/es.po | 2 +- src/bin/pg_config/po/it.po |16 +- src/bin/pg_controldata/po/es.po | 181 +- src/bin/pg_controldata/po/fr.po | 183 +- src/bin/pg_controldata/po/it.po | 178 +- src/bin/pg_ctl/po/es.po | 411 +- src/bin/pg_ctl/po/fr.po | 431 +- src/bin/pg_ctl/po/it.po | 379 +- src/bin/pg_dump/po/es.po | 1182 +-- src/bin/pg_dump/po/fr.po | 1986 ++-- src/bin/pg_dump/po/it.po | 1189 +-- src/bin/pg_resetwal/po/es.po | 267 +- src/bin/pg_resetwal/po/fr.po | 292 +- src/bin/pg_rewind/po/es.po | 260 +- src/bin/pg_rewind/po/fr.po | 176 +- src/bin/pg_rewind/po/it.po | 262 +- src/bin/pg_test_fsync/nls.mk | 2 +- src/bin/pg_test_fsync/po/es.po | 189 + src/bin/pg_test_fsync/po/fr.po | 187 + src/bin/pg_test_timing/nls.mk| 2 +- src/bin/pg_test_timing/po/es.po |81 + src/bin/pg_test_timing/po/fr.po |79 + src/bin/pg_waldump/nls.mk| 2 +- src/bin/pg_waldump/po/es.po | 251 + src/bin/pg_waldump/po/fr.po | 251 + src/bin/psql/po/es.po| 3704 src/bin/psql/po/fr.po| 6551 +++--- src/bin/psql/po/it.po| 3217 --- src/bin/scripts/po/es.po | 444 +- src/bin/scripts/po/fr.po | 500 +- src/bin/scripts/po/it.po | 376 +- src/interfaces/ecpg/ecpglib/po/es.po | 4 +- src/interfaces/ecpg/preproc/po/es.po | 160 +- src/interfaces/ecpg/preproc/po/fr.po | 166 +- src/interfaces/ecpg/preproc/po/it.po | 184 +- src/interfaces/libpq/po/de.po| 274 +- src/interfaces/libpq/po/es.po| 634 +- src/interfaces/libpq/po/fr.po| 540 +- src/interfaces/libpq/po/it.po| 439 +- src/pl/plperl/po/es.po |99 +- src/pl/plperl/po/fr.po | 119 +- src/pl/plperl/po/it.po | 102 +- src/pl/plpgsql/src/po/es.po | 344 +- src/pl/plpython/po/es.po | 219 +- src/pl/plpython/po/fr.po | 261 +- src/pl/plpython/po/it.po | 203 +- src/pl/tcl/po/es.po | 104 +- src/pl/tcl/po/fr.po | 124 +- src/pl/tcl/po/it.po |90 +- 60 files changed, 34345 insertions(+), 26571 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Stamp 10beta2.
Stamp 10beta2. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/42171e2cd23c8307bbe0ec64e901f58e297db1c3 Modified Files -- configure | 18 +- configure.in | 2 +- doc/bug.template | 2 +- src/include/pg_config.h.win32 | 6 +++--- 4 files changed, 14 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.
On Mon, Jul 10, 2017 at 10:01 PM, Heikki Linnakangas wrote: > On 07/10/2017 01:27 PM, Masahiko Sawada wrote: >> >> This commit seems be cause of the documentation compilation error. I >> think is missing. >> >> ... >> >> Attached small patch fixes this. > > > Thanks, committed! > > Strangely, it worked on my system, despite that clear mistake. Looks like > the 'osx' tool is more strict than what I had installed. I have now also > installed opensp, so won't make this mistake again. > Thank you! Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
