| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Query Failed, out of memory |
| Date: | 2006-10-05 16:01:24 |
| Message-ID: | 14200.1160064084@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mark Woodward" <pgsql(at)mohawksoft(dot)com> writes:
> psql -p 5435 -U pgsql -t -A -c "select client, item, rating, day from
> ratings order by client" netflix > netflix.txt
> My question, it looks like the kernel killed psql, and not postmaster.
Not too surprising.
> Question, is this a bug in psql?
It's really a libpq design issue: since libpq provides random access to
a PGresult, and has no mechanism for handling failures after returning
the PGresult to the client, it has to slurp the whole query result into
memory first.
FWIW, there's a feature in CVS HEAD to instruct psql to try to use a
cursor to break up huge query results like this. For the moment I'd
suggest using COPY instead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-10-05 16:12:56 | Re: Query Failed, out of memory |
| Previous Message | AgentM | 2006-10-05 16:00:15 | Re: Query Failed, out of memory |