[COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.

2017-07-10 Thread Heikki Linnakangas
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 w

Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.

2017-07-10 Thread Masahiko Sawada
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,

[COMMITTERS] pgsql: Fix COPY's handling of transition tables with indexes.

2017-07-10 Thread Andrew Gierth
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 Fet

[COMMITTERS] pgsql: Fix check for empty hostname.

2017-07-10 Thread Heikki Linnakangas
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.or

[COMMITTERS] pgsql: Fix missing tag in the docs.

2017-07-10 Thread Heikki Linnakangas
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 F

Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.

2017-07-10 Thread Heikki Linnakangas
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 str

[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared

2017-07-10 Thread Tom Lane
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 t

[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared

2017-07-10 Thread Tom Lane
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 t

[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared

2017-07-10 Thread Tom Lane
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 t

[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared

2017-07-10 Thread Tom Lane
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 t

[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared

2017-07-10 Thread Tom Lane
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 t

[COMMITTERS] pgsql: On Windows, retry process creation if we fail to reserve shared

2017-07-10 Thread Tom Lane
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 t

[COMMITTERS] pgsql: Translation updates

2017-07-10 Thread Alvaro Herrera
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 ---

[COMMITTERS] pgsql: Stamp 10beta2.

2017-07-10 Thread Tom Lane
Stamp 10beta2. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/42171e2cd23c8307bbe0ec64e901f58e297db1c3 Modified Files -- configure | 18 +- configure.in | 2 +- doc/bug.template | 2 +- sr

Re: [COMMITTERS] pgsql: Allow multiple hostaddrs to go with multiple hostnames.

2017-07-10 Thread Masahiko Sawada
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