agora inbox for pgpool-committers@postgresql.org  
help / color / mirror / Atom feed
pgpool: Fix  file deletion command in recovery_1st_stage.sample.
4+ messages / 1 participants
[nested] [flat]

* pgpool: Fix  file deletion command in recovery_1st_stage.sample.
@ 2025-09-10 06:16  Taiki Koshino <koshino@sraoss.co.jp>
  0 siblings, 0 replies; 4+ messages in thread

From: Taiki Koshino @ 2025-09-10 06:16 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

Fix  file deletion command in recovery_1st_stage.sample.

In the recovery_1st_stage script, the file deletion command has been modified.
Previously, files under ARCHIVEDIR were deleted using "rm *", but when the total size of the target files exceeded ARG_MAX, it resulted in an "Argument list too long" error and caused the recovery_1st_stage script to fail.
By switching to the find command to delete files one by one, this error is avoided.

Discussion: https://github.com/pgpool/pgpool2/issues/94
Backpatch-through: v4.2

Branch
------
V4_2_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=bb9accfd68fe2ac2a384be8f698ee90a28f69...

Modified Files
--------------
src/sample/scripts/recovery_1st_stage.sample | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)



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

* pgpool: Fix  file deletion command in recovery_1st_stage.sample.
@ 2025-09-10 06:18  Taiki Koshino <koshino@sraoss.co.jp>
  0 siblings, 0 replies; 4+ messages in thread

From: Taiki Koshino @ 2025-09-10 06:18 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

Fix  file deletion command in recovery_1st_stage.sample.

In the recovery_1st_stage script, the file deletion command has been modified.
Previously, files under ARCHIVEDIR were deleted using "rm *", but when the total size of the target files exceeded ARG_MAX, it resulted in an "Argument list too long" error and caused the recovery_1st_stage script to fail.
By switching to the find command to delete files one by one, this error is avoided.

Discussion: https://github.com/pgpool/pgpool2/issues/94
Backpatch-through: v4.2

Branch
------
V4_3_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=732d38525b34e68123f8bee27abf56866a11c...

Modified Files
--------------
src/sample/scripts/recovery_1st_stage.sample | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)



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

* pgpool: Fix  file deletion command in recovery_1st_stage.sample.
@ 2025-09-10 06:19  Taiki Koshino <koshino@sraoss.co.jp>
  0 siblings, 0 replies; 4+ messages in thread

From: Taiki Koshino @ 2025-09-10 06:19 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

Fix  file deletion command in recovery_1st_stage.sample.

In the recovery_1st_stage script, the file deletion command has been modified.
Previously, files under ARCHIVEDIR were deleted using "rm *", but when the total size of the target files exceeded ARG_MAX, it resulted in an "Argument list too long" error and caused the recovery_1st_stage script to fail.
By switching to the find command to delete files one by one, this error is avoided.

Discussion: https://github.com/pgpool/pgpool2/issues/94
Backpatch-through: v4.2

Branch
------
V4_4_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=eaa9bdf1f25436f7f6f675c01135c2625cf09...

Modified Files
--------------
src/sample/scripts/recovery_1st_stage.sample | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)



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

* pgpool: Fix  file deletion command in recovery_1st_stage.sample.
@ 2025-09-10 06:20  Taiki Koshino <koshino@sraoss.co.jp>
  0 siblings, 0 replies; 4+ messages in thread

From: Taiki Koshino @ 2025-09-10 06:20 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

Fix  file deletion command in recovery_1st_stage.sample.

In the recovery_1st_stage script, the file deletion command has been modified.
Previously, files under ARCHIVEDIR were deleted using "rm *", but when the total size of the target files exceeded ARG_MAX, it resulted in an "Argument list too long" error and caused the recovery_1st_stage script to fail.
By switching to the find command to delete files one by one, this error is avoided.

Discussion: https://github.com/pgpool/pgpool2/issues/94
Backpatch-through: v4.2

Branch
------
V4_5_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=063b7e111668023eb9a31ed02a5f3cc6a61e1...

Modified Files
--------------
src/sample/scripts/recovery_1st_stage.sample | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)



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


end of thread, other threads:[~2025-09-10 06:20 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-09-10 06:16 pgpool: Fix  file deletion command in recovery_1st_stage.sample. Taiki Koshino <koshino@sraoss.co.jp>
2025-09-10 06:18 pgpool: Fix  file deletion command in recovery_1st_stage.sample. Taiki Koshino <koshino@sraoss.co.jp>
2025-09-10 06:19 pgpool: Fix  file deletion command in recovery_1st_stage.sample. Taiki Koshino <koshino@sraoss.co.jp>
2025-09-10 06:20 pgpool: Fix  file deletion command in recovery_1st_stage.sample. Taiki Koshino <koshino@sraoss.co.jp>

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