Paul Cioanca

@Exagone313 - thanks for the workaround! This'll surely help out others which are impacted by the same issue. Unfortunately when dealing with very large backups, or backups created using `pg_backupall`,...

Hi @Gipetto - thanks for reporting this! Will investigate - in the meantime, to help narrow-down on any edge-cases, could you also provide the Docker runtime version used to build...

@rbkayz unfortunately we were not able to reproduce the problem across Ubuntu, NixOS, and MacOS. Using `dos2unix` across these systems doesn't seem to modify the file whatsoever - does it...

@Gipetto @rbkayz - just merged a fix to ensure that the entrypoint is flagged as executable during the build step. A bit of a long shot but given we couldn't...

Hi @Towerful - thanks for reporting this! We're investigating

Hi folks - just want to confirm some data points. Is this running on Fly.io, or a dockerized setup? We have a theory that network latency might play a role...

I see, thank you! We've managed to reproduce the behaviour and are actively looking into this

> Sorry I missed this earlier - gave it a quick skim and looks great. Any changes needed to bring it up to speed? > > @supabase/postgres any concerns with...

> Looks great! 👍I guess we don't need to include [Testinfra](https://github.com/supabase/postgres/blob/32e93b510517ecb87c77a6cbbddf358acf3f0e10/.github/workflows/testinfra.yml#L8C19-L8C19) tests since this should only affect PG stuff? Yep! This would run as a parallel check to those, so...

Will merge after tomorrow's (Jun 13th) prod deploy, to have more ample time for testing the pg_upgrade scripts