pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gary Doades <gpd@gpdnet.co.uk>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres backend using huge amounts of ram
Date: Fri, 26 Nov 2004 19:42:50 +0000
Message-ID: <41A7873A.7000202@gpdnet.co.uk> (raw)
In-Reply-To: <10676.1101497134@sss.pgh.pa.us>
References: <41A6420D.2030307@gpdnet.co.uk>
	<10676.1101497134@sss.pgh.pa.us>

Tom Lane wrote:
> 
> It's also worth noting that work_mem is temporarily set to
> maintenance_work_mem, which you didn't tell us the value of:
> 
It's left at the default. (16384).

This would be OK if that is all it used for this type of thing.

> 
> 
> My recollection is that hash join chooses hash table partitions partly
> on the basis of the estimated number of input rows.  Since the estimate
> was way off, the actual table size got out of hand a bit :-(

A bit!!

The really worrying bit is that a normal (ish) query also exhibited the 
same behaviour. I'm a bit worried that if the stats get a bit out of 
date so that the estimate is off, as in this case, a few backends trying 
to get this much RAM will see the server grind to a halt.

Is this a fixable bug? It seems a fairly high priority, makes the server 
go away, type bug to me.

If you need the test data, I could zip the two tables up and send them 
somewhere....

Thanks,
Gary.



view thread (4+ messages)

Message-ID: <41A7873A.7000202@gpdnet.co.uk>
Permalink:  ../41A7873A.7000202@gpdnet.co.uk/
Also on:    postgresql.org/message-id/41A7873A.7000202@gpdnet.co.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gpd@gpdnet.co.uk, tgl@sss.pgh.pa.us
  Subject: Re: Postgres backend using huge amounts of ram
  In-Reply-To: <41A7873A.7000202@gpdnet.co.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox