Re: Regression test fails when BLCKSZ is 1kB

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Regression test fails when BLCKSZ is 1kB
Date: 2008-04-22 09:13:30
Message-ID: 480DAC3A.5010409@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane napsal(a):

> Another possible answer is to change the minimum to be just 64K always.
> I'm not certain that it's really sensible to tie the minimum work_mem to
> BLCKSZ --- I don't think we do anything where work_mem is controlling a
> pool of page buffers, do we?

Yeah, I try to find all usage and it seems everything is related to tuplestore,
Bitmap or Hash join. I think we can set 64K set limit without any problem.

By the way is any reason to have work_mem * 1024 "everywhere" when we have unit
support in GUC?

Zdenek

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message PFC 2008-04-22 10:13:53 Per-table random_page_cost for tables that we know are always cached
Previous Message Zdenek Kotala 2008-04-22 08:38:03 Re: Regression test fails when BLCKSZ is 1kB