Hi, On 2022-03-29 17:19:44 -0400, Robert Haas wrote: > On Tue, Mar 29, 2022 at 4:36 PM Thomas Munro <thomas.mu...@gmail.com> wrote: > > It failed: > > > > https://cirrus-ci.com/task/5567070686412800 > > https://api.cirrus-ci.com/v1/artifact/task/5567070686412800/log/contrib/basebackup_to_shell/tmp_check/log/001_basic_primary.log > > https://api.cirrus-ci.com/v1/artifact/task/5567070686412800/log/contrib/basebackup_to_shell/tmp_check/log/regress_log_001_basic > > Hmm. The log here is not very informative. It just says that the first > time we tried to use the 'shell' target, it timed out. I suppose the > most obvious explanation for that is that the shell command we > executed timed out: > > qq{type con > "$escaped_backup_path\\\\%f"} > > But why should that be so? Does 'type con' not respond to EOF?
This is trying to write stdin into a file? I think the problem may be that con doesn't represent stdin, it it's console input. I think consoles are a separate thing from stdin on windows - you can have console input, even while stdin is coming from a file or such. Didn't immediate find a reference to a cat equivalent. Maybe just gzip the file? That can read from stdin across platforms afaict. Greetings, Andres Freund
