On Mon, Feb 9, 2009 at 2:40 PM, Matt Magoffin <postgresql.org@xxxxxxx> wrote: >>> Yes... and indeed changing vm.overcommit_ratio to 80 does allow that >>> previously-failing query to execute successfully. Do you think this is >>> also what caused the out-of-memory error we saw today just when a >>> transaction was initiated? >> >> Curious, what's the explain analyze look like for that one? > > Do you mean the transaction initiation? I'm not sure how to get an EXPLAIN > for that, the application never got to do anything, from the application > side it failed with out-of-memory while trying to open the connection. Or, > the most precise I have is that in the JDBC driver, it failed at No, explain analyze for the query that wouldn't execute before but now does, with, I assume, a large work_mem. I'd like to see how it differes from the one with smaller work_mem. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
