On 2013-03-20, David Rees wrote:
> On Wed, Mar 20, 2013 at 12:37 PM, David Rees wrote:
>> PostgreSQL 8.4.16 on CentOS 5.9.
>>
>> I've run into a situation where executing a \COPY from psql will hang
>> and at that point it's impossible to terminate the COPY command.
>
> Some additional notes:
>
>
David Rees writes:
> On Wed, Mar 20, 2013 at 12:37 PM, David Rees wrote:
>> PostgreSQL 8.4.16 on CentOS 5.9.
>>
>> I've run into a situation where executing a \COPY from psql will hang
>> and at that point it's impossible to terminate the COPY command.
> Some additional notes:
> Running psql o
On Wed, Mar 20, 2013 at 12:37 PM, David Rees wrote:
> PostgreSQL 8.4.16 on CentOS 5.9.
>
> I've run into a situation where executing a \COPY from psql will hang
> and at that point it's impossible to terminate the COPY command.
Some additional notes:
Running psql on the same LAN for some reason
On Wed, Mar 20, 2013 at 1:12 PM, Martín Marqués
wrote:
> What happens if you use COPY ... FROM with the same data?
I will try that, but if you look at pg_stat_activity the full command
is a COPY ( Are you sure the process hangs (strange thing is that you can't
> terminate the backend)? Could it
2013/3/20 David Rees :
> PostgreSQL 8.4.16 on CentOS 5.9.
>
> I've run into a situation where executing a \COPY from psql will hang
> and at that point it's impossible to terminate the COPY command.
>
> I've tried pg_cancel_backend and pg_terminalte_backend - even sending
> the process itself a TER
PostgreSQL 8.4.16 on CentOS 5.9.
I've run into a situation where executing a \COPY from psql will hang
and at that point it's impossible to terminate the COPY command.
I've tried pg_cancel_backend and pg_terminalte_backend - even sending
the process itself a TERM signal.
Sending the process KILL
