| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [ADMIN] Getting the initdb parameter values |
| Date: | 2010-04-13 17:57:53 |
| Message-ID: | 4BC4B0A1.2090604@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-sql |
As I read it, it doesn't matter what the value was originally, it's
what's in postgresql.conf _now_ that matters.
This is a resource allocation: I suspect there's no limit on how much of
your (often precious) memory you wish to set aside for this.
On 04/13/2010 07:01 AM, Satish Burnwal (sburnwal) wrote:
> What you have mentioned is already there in postgresql.conf file. I want
> to know whats the max value allowed ? Doc seems to be saying that max
> allowed value is determined during initdb. How to get this max allowed
> value ?
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julio Leyva | 2010-04-13 18:01:35 | Re: Getting the initdb parameter values |
| Previous Message | Greg Smith | 2010-04-13 17:13:58 | Re: Getting the initdb parameter values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julio Leyva | 2010-04-13 18:01:35 | Re: Getting the initdb parameter values |
| Previous Message | Greg Smith | 2010-04-13 17:13:58 | Re: Getting the initdb parameter values |