Re: Libpq COPY optimization

From: "Alon Goldshuv" <agoldshuv(at)greenplum(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Libpq COPY optimization
Date: 2006-01-12 15:10:06
Message-ID: BFEC3DEE.BED3%agoldshuv@greenplum.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

> It's not enough better, because it will still deadlock given a
> sufficiently large message-to-send. I don't think you can postpone
> the clearing-input action until after all the data is sent.
>
> regards, tom lane

Please help me understand this better. It appears to me that when the
client->backend pipe fills up, pqSendSome() consumes any incoming
NOTICE/WARNING messages before waiting, which should prevent deadlock. I'll
look at the code again, maybe I missed something.

Thx,
Alon.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-01-12 21:53:09 Re: Checkpoint question
Previous Message Qingqing Zhou 2006-01-12 09:50:30 Re: Checkpoint question