| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: Max backend limits cleaned up |
| Date: | 1999-02-22 17:51:17 |
| Message-ID: | 9938.919705877@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Yeah, I was thinking about that myself. I left the default -N setting
>> at 64 on the theory that people who had gone to the trouble of making
>> sure they had proper kernel configurations should not get surprised by
>> v6.5 suddenly reducing the default number-of-backends limit.
> The default was always 32, right, so they should not be suprised if they
> don't up the limit to 64.
No, the default MaxBackendId was 64 (unless that's been changed
recently?). A stock installation of 6.4 will support 64 backends
assuming that you have adequate kernel settings for that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-02-22 17:54:47 | Re: [HACKERS] Re: Max backend limits cleaned up |
| Previous Message | Tom Lane | 1999-02-22 17:40:52 | Re: Anyone understand shared-memory space usage? |