Re: Query Failed, out of memory

From: AgentM <agentm(at)themactionfaction(dot)com>
To: PostgreSQL-development hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Query Failed, out of memory
Date: 2006-10-05 16:00:15
Message-ID: F4A61655-C051-4AE0-9D0E-DBCB588D9E61@themactionfaction.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Oct 5, 2006, at 11:56 , Mark Woodward wrote:

> I am using the netflix database:
> Table "public.ratings"
> Column | Type | Modifiers
> --------+----------+-----------
> item | integer |
> client | integer |
> day | smallint |
> rating | smallint |
>
>
> The query was executed as:
> 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. The
> postgresql log file complained about a broken pipe.
>
> Question, is this a bug in psql? It took over 4 hours of run time
> before
> the crash.

The OOM killer kills a process based on some heuristics but it is
just a guess. For reliable behavior, configure Linux to 1) disable
the OOM killer 2) stop overcommitting memory. Then, you should be
able to get the results you require.

-M

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-10-05 16:01:24 Re: Query Failed, out of memory
Previous Message Martijn van Oosterhout 2006-10-05 15:59:52 Re: Query Failed, out of memory