| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "jayknowsunix(at)gmail(dot)com" <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Problems with PG 9.3 |
| Date: | 2014-08-26 19:37:40 |
| Message-ID: | CAOR=d=1Bce+gUvwz_xOFd9Mb6H+2ED8kvey+MTtgSeBkRyrcqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Aug 26, 2014 at 1:32 PM, Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> wrote:
> Scott,
> Thanks for such a valuable information. I will have a look into it and have
> it debugged.
>
> But now things have started slowing down really. Some programs have started
> to throw errors like
>
> ERROR: DB COPY failed: DBD::Pg::db pg_endcopy
> failed: ERROR: out of shared memory
> HINT: You might need to increase max_locks_per_transaction.
>
>
> These were things which were working before with higher memory settings. And
> some are just running slow, slow means literally slow even though they are
> connected via netstat and all.
OK increasing max locks per transaction is pretty safe. What did you
change shared_mem from and too? Setting it a bit higher isn't terribly
dangerous, like work_mem x max_conns can be.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dhruv Shukla | 2014-08-26 19:44:11 | Re: Problems with PG 9.3 |
| Previous Message | Dhruv Shukla | 2014-08-26 19:32:49 | Re: Problems with PG 9.3 |