pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Skip pg_baseback long filename test if path too long on Windows
7+ messages / 1 participants
[nested] [flat]

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1fa25ce70f0901b5b55b1fe9ca10cb3b9905db97

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/b94d70a632aabb02079f094b9c9a32f4f6b8c984

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2e99ce68bcd22d41d417cdd05ccd47d54c30a2a0

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 24 +++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2d3983aea5db679fdd1b286ded792692580e8f3f

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 24 +++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9ebe6fdc5c684c21a44aeaf98837c54d7415ca2a

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 24 +++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/fb0f05576a0a6a452fe206a9e1d181f8f82dd882

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Skip pg_baseback long filename test if path too long on Windows
@ 2023-07-06 16:37  Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 7+ messages in thread

From: Andrew Dunstan @ 2023-07-06 16:37 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c0cb12f9e7b33bbcd64cc93d0811bc10e17e5452

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread


end of thread, other threads:[~2023-07-06 16:37 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>
2023-07-06 16:37 pgsql: Skip pg_baseback long filename test if path too long on Windows Andrew Dunstan <andrew@dunslane.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox