pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: docs: clarify handling of column lists in COPY TO/FROM

2019-12-21 Thread Bruce Momjian
docs: clarify handling of column lists in COPY TO/FROM Previously it was unclear how COPY FROM handled cases where not all columns were specified, or if the order didn't match. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected]

pgsql: C comment: clarify why psql's help/exit/quit must alone

2019-12-21 Thread Bruce Momjian
C comment: clarify why psql's help/exit/quit must alone Document why no indentation and why no non-whitespace postfix is supported. Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4376fdbae11de9333012a31ba8d3a4f4b5d7a692 Modified Files -

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea

pgsql: In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't

2019-12-21 Thread Tom Lane
In pgwin32_open, loop after ERROR_ACCESS_DENIED only if we can't stat. This fixes a performance problem introduced by commit 6d7547c21. ERROR_ACCESS_DENIED is returned in some other cases besides the delete-pending case considered by that commit; notably, if the given path names a directory instea