Re: maintenance_work_mem memory constraint?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: maintenance_work_mem memory constraint?
Date: 2007-11-26 18:02:14
Message-ID: 23458.1196100134@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bernd Helmle <mailings(at)oopsware(dot)de> writes:
> ... But isn't it worth to special case the
> code in grow_memtuples() (and maybe other places where sort is likely to
> use more RAM), so that we can remove this constraint on 64-Bit systems with
> many RAM built in? Or am I missing something very important?.

AFAICS this patch can increase the number of sortable tuples by at most 2X
(less one). That doesn't seem worth getting very worked up about ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message mac_man2005 2007-11-26 18:08:55 Re: Replacement Selection
Previous Message Tom Lane 2007-11-26 17:48:20 Re: 8.3devel slower than 8.2 under read-only load