Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception - Mailing list pgsql-performance

From Matthew Wakeling
Subject Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date
Msg-id alpine.DEB.1.10.0808282104410.4454@aragorn.flymine.org
Whole thread Raw
In response to Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception  (david@lang.hm)
List pgsql-performance
On Thu, 28 Aug 2008, david@lang.hm wrote:
> I just asked on the kernel mailing list and Alan Cox responded.
>
> he is saying that you are correct, it only allocates against the total
> available, it doesn't actually allocate ram.

That was remarkably graceful of you. Yes, operating systems have worked
that way for decades - it's the beauty of copy-on-write.

> but you do need to allocate more swap as the total memory 'used' can be
> significantly higher that with overcommit on.

Yes, that's right.

Matthew

--
Note: some countries impose serious penalties for a conspiracy to overthrow
      the political system. THIS DOES NOT FIX THE VULNERABILITY.
                          -- http://lcamtuf.coredump.cx/soft/trash/1apr.txt

pgsql-performance by date:

Previous
From: "Fernando Hevia"
Date:
Subject: Re: Best hardware/cost tradoff?
Next
From: Craig James
Date:
Subject: Re: Best hardware/cost tradoff?