| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Best <nbest(at)ci(dot)uchicago(dot)edu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: \copy: unexpected response (4) |
| Date: | 2009-08-07 15:49:53 |
| Message-ID: | 22987.1249660193@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Neil Best <nbest(at)ci(dot)uchicago(dot)edu> writes:
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
> psql:copy.sql:8059525: \copy: unexpected response (4)
Hmm. It looks like psql could get into an infinite loop if the server
failed to exit COPY IN mode for some reason, but it's not at all clear
how that could happen (or what to do about it). What server version
and what psql version is this? What does the server's log show?
Can you provide a reproducible test case?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Best | 2009-08-07 16:08:07 | Re: \copy: unexpected response (4) |
| Previous Message | Neil Best | 2009-08-07 14:37:00 | \copy: unexpected response (4) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-08-07 15:54:17 | Re: Fixing geometic calculation |
| Previous Message | Jaime Casanova | 2009-08-07 15:44:44 | Re: Filtering dictionaries support and unaccent dictionary |