On Sun, Mar 8, 2009 at 6:37 PM, Christian Schröder <cs@xxxxxxxxx> wrote: > Tom Lane wrote: >> >> No, they're not the same; NOT IN has different semantics for nulls. >> > > But in this case the column in the subselect has a not-null constraint. Does > the planner recognize this constraint? not in this case, afaik >> You're probably at the threshold where it doesn't think the hashtable >> would fit in work_mem. work_mem constraints amount of memory allocated per connection, hence you can run out of memory if too many connections try to use too much of it at the same time, that's why it is advisable to set work_mem per connection/query, should the connection/query require more. -- GJ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
