From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Charles Martin <ssappeals(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Trouble Upgrading Postgres |
Date: | 2018-11-06 00:37:55 |
Message-ID: | 2293f666-c8f7-52d4-14fc-8e27630aac14@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/5/18 8:50 AM, Charles Martin wrote:
> Daniel said:
>
> This appears to be the case. I ran:
>
> SELECT max(length(docfilecontents::text)) FROM docfile;
> and after a very long time, got:
> ERROR: invalid memory alloc request size 1636085512 SQL state: XX000
>
> Adrian said:
>>> Ok, thanks for explaining this. Here is the current value:
>>> "shared_buffers""131072""8kB"
> >It should be a single value something like this for the default:
> >shared_buffers = 128MB
>
> The results I pasted were from:
>
> SELECT * FROM pg_settings
>
> Maybe I didn't get it the right way.
>
> The system has only 4GB of RAM. I read that a reasonable swap size is
> 1/4 of RAM, so I've created a swap file of 1GB.
I would change the shared_buffers setting to 128MB and retry.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2018-11-06 02:05:24 | CREATE OR REPLACE FUNCTION statement just sitting there |
Previous Message | Tatsuo Ishii | 2018-11-05 23:43:03 | Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan |