From: | Shreeyansh dba <shreeyansh2014(at)gmail(dot)com> |
---|---|
To: | Raghu Ram <raghuchennuru(at)gmail(dot)com> |
Cc: | christian(dot)echerer(at)manroland-web(dot)com, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Out of shared memory while creating a backup with pg_dump |
Date: | 2014-09-24 11:14:00 |
Message-ID: | CAGDYbUPJA4W43mEHjNb9-jpToZJm_-N_99B__qrj1RzFqNcebg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Sep 24, 2014 at 4:03 PM, Raghu Ram <raghuchennuru(at)gmail(dot)com> wrote:
> On Wed, Sep 24, 2014 at 2:35 PM, <christian(dot)echerer(at)manroland-web(dot)com>
> wrote:
>
>> Hi,
>>
>> while creating a backup with pg_dump and parallel write accesses to the
>> database following error occured:
>> 2014-09-24 07:46:46 ... ERROR: out of shared memory
>> 2014-09-24 07:46:46 ... HINT: You might need to increase
>> max_pred_locks_per_transaction.
>>
>>
>
> This a new parameter introduced in PostgreSQL 9.1. This issue will be
> resolved by increasing "max_pred_locks_per_transaction" parameter value
> from default of 64 to 256 in PostgreSQL.conf file.
>
>
Along with this above parameters also change from max_wal_sender=1 to
max_wal_sender=5
Hope this will resolve your issue.
Thanks & Regards ,
Chetan Sharma
www.shreeyansh.com
Thanks & Regards
> Raghu Ram
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Raj Gandhi | 2014-09-24 13:26:36 | Re: format() function with string_agg |
Previous Message | Raghu Ram | 2014-09-24 10:33:47 | Re: Out of shared memory while creating a backup with pg_dump |