2009/3/9 Christian Schröder c...@deriva.de:
I understand why this is advisable; however, something inside me hates the
idea to put this kind of database specific stuff inside an application. How
about portability? Why does the application developer have to know about
database internals? He
Scott Marlowe wrote:
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.
Definitely.
I understand why this is advisable; however,
2009/3/9 Christian Schröder c...@deriva.de:
Scott Marlowe wrote:
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.
Definitely.
I
2009/3/6 Christian Schröder c...@deriva.de
Hi list,
if I want to find all records from a table that don't have a matching
record in another table there are at least two ways to do it: Using a left
outer join or using a subselect. I always thought that the planner would
create identical plans
On Mon, Mar 09, 2009 at 11:45:38AM +0100, Christian Schröder wrote:
Scott Marlowe wrote:
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.
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?
You're probably at the threshold where it doesn't think the hashtable
would fit in
On Sun, Mar 8, 2009 at 6:37 PM, Christian Schröder c...@deriva.de 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,
On Sun, Mar 8, 2009 at 12:47 PM, Grzegorz Jaśkiewicz gryz...@gmail.com wrote:
work_mem constraints amount of memory allocated per connection, hence
Actually, it's per sort. And there can be 1 sort per query.
you can run out of memory if too many connections try to use too much
of it at the
=?ISO-8859-1?Q?Christian_Schr=F6der?= c...@deriva.de writes:
if I want to find all records from a table that don't have a matching
record in another table there are at least two ways to do it: Using a
left outer join or using a subselect. I always thought that the planner
would create
Hi list,
if I want to find all records from a table that don't have a matching
record in another table there are at least two ways to do it: Using a
left outer join or using a subselect. I always thought that the planner
would create identical plans for both approaches, but actually they are
On Thu, Mar 5, 2009 at 11:25 PM, Christian Schröder c...@deriva.de wrote:
Hi list,
if I want to find all records from a table that don't have a matching record
in another table there are at least two ways to do it: Using a left outer
join or using a subselect. I always thought that the planner
11 matches
Mail list logo
