Re: pg_restore COPY error handling

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <sfrost(at)snowman(dot)net>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_restore COPY error handling
Date: 2006-02-02 02:33:29
Message-ID: 1488.24.211.165.134.1138847609.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane said:
>
> Also, it might be possible to depend on whether libpq has entered the
> "copy in" state. I'm not sure this works very well, because if there's
> an error in the COPY command itself (not in the following data) then we
> probably don't ever get into "copy in" state.
>

Could we not refrain from sending data if we detect that we are not in copy
in state?

cheers

andrew

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Stephen Frost 2006-02-02 02:45:41 Re: pg_restore COPY error handling
Previous Message Bruce Momjian 2006-02-02 02:24:19 Re: TODO-Item: B-tree fillfactor control