From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
Cc: | t-ishii(at)sra(dot)co(dot)jp, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Open 6.5 items |
Date: | 1999-06-04 21:51:12 |
Message-ID: | 25136.928533072@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Vadim Mikheev <vadim(at)krs(dot)ru> writes:
> Tom Lane wrote:
>> Right now, the postmaster will let you set any combination of -B and -N
>> you please. But it seems obvious that there is some minimum number of
>> buffers per backend below which things aren't going to work very well.
>> I wonder whether the postmaster startup code ought to enforce a minimum
>> ratio, say -B at least twice -N ? I have no idea what an appropriate
> ^^^^^^^^^^^^^^
> It's enough for select from single table using index, so it's
> probably good ratio.
I've added a check in postmaster.c to require -B to be at least twice
-N, per this discussion. It also enforces a minimum -B of 16 no matter
how small -N is. I pulled that number out of the air --- anyone have an
idea whether some other number would be better?
The current default values of -B 64, -N 32 are not affected. However,
since the -N default is easily configurable, I wonder whether we should
move the default -B value into config.h as well...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 1999-06-04 22:42:03 | Re: Backend problem with large objects |
Previous Message | Massimo Dal Zotto | 1999-06-04 21:46:38 | contrib code for 6.5 |