Re: Hang issue when COPY to/from an unopened FIFO

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kenan Yao <kyao(at)pivotal(dot)io>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hang issue when COPY to/from an unopened FIFO
Date: 2016-07-14 14:20:42
Message-ID: 1619.1468506042@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kenan Yao <kyao(at)pivotal(dot)io> writes:
> -- mkfifo /tmp/test.dat # bash
> copy pg_class to '/tmp/test.dat';
> -- try pg_cancel_backend or pg_terminate_backend from other sessions

This does not seem like a supported case to me. I see few if any reasons
to want to do that rather than doing copy-to-program or copy-to-client.
We're certainly not going to want to add any overhead to the COPY code
paths in order to allow it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-07-14 15:24:38 Re: Hang issue when COPY to/from an unopened FIFO
Previous Message Simon Riggs 2016-07-14 13:54:05 Re: pg_xlogdump follow into the future