This is a multi-part message in MIME format.
------=_NextPart_000_0074_01C7987C.E42057C0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hi again!
It seems that the problem was the max_fsm_relations parameter which was
increased
I still do not understand why in the past I received always the message:
ERROR: out of shared memory
Is this an appropriate message for the need for increasing this parameter?
With best regards,
Sorin C.
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Adam Tauno Williams
Sent: Friday, May 11, 2007 9:42 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] increasing of the shared memory does not solve
theproblem of "OUT of shared memory"
> I increased significantly the number of shared buffers from 3000 to
> 100 000 (80Mb)
> Also I increased the max_locks_per_transaction from 64 to 10 000.
> I still receive the same error form Postgres:
> org.postgresql.util.PSQLException: ERROR: out of shared memory
> Is this message appropriate to the real cause of the problem or the
> reason of the failure is actually other than what is displayed in this
> message?
>
Maybe you've got an application that is doing a BEGIN WORK, but never
doing a rollback or commit?
--
Adam Tauno Williams, Network & Systems Administrator
Consultant - http://www.whitemiceconsulting.com
Developer - http://www.opengroupware.org
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
------=_NextPart_000_0074_01C7987C.E42057C0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
lang=3DEN-US
style=3D'font-size:10.0pt'>Hi again!
lang=3DEN-US
style=3D'font-size:10.0pt'>
lang=3DEN-US
style=3D'font-size:10.0pt'>It seems that the problem was the =
lang=3DEN-GB =
style=3D'font-weight:bold'>max_fsm_relations
lang=3DEN-GB> parameter which was increased
lang=3DEN-US>
lang=3DEN-GB
style=3D'font-size:10.0pt'>
lang=3DEN-GB
style=3D'font-size:10.0pt'>I still do not understand why in the past I =
received
always the message:
lang=3DEN-GB
style=3D'font-size:10.0pt'>ERROR: out of shared =
memory
lang=3DEN-GB
style=3D'font-size:10.0pt'>
lang=3DEN-GB
style=3D'font-size:10.0pt'>Is this an appropriate message for the need =
for
increasing this parameter?
lang=3DEN-GB
style=3D'font-size:10.0pt'>
lang=3DEN-GB
style=3D'font-size:10.0pt'>With best =
regards,
lang=3DEN-GB
style=3D'font-size:10.0pt'>Sorin C.
lang=3DEN-GB
style=3D'font-size:10.0pt'>
lang=3DEN-US
style=3D'font-size:10.0pt'>-----Original Message-----
From: pgsql-admin-owner@postgresql.org =
[mailto:pgsql-admin-owner@postgresql.org]
On Behalf Of Adam Tauno Williams
Sent: Friday, May 11, 2007 9:42 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] increasing of the shared memory does not solve =
theproblem
of "OUT of shared memory"
style=3D'font-size:
10.0pt'>
style=3D'font-size:
10.0pt'>
style=3D'font-size:
10.0pt'>
style=3D'font-size:
10.0pt'>> I increased significantly the number of shared buffers from =
3000
to
style=3D'font-size:
10.0pt'>> 100 000 (80Mb)
style=3D'font-size:
10.0pt'>> Also I increased the max_locks_per_transaction from =
64 to 10
000.
style=3D'font-size:
10.0pt'>> I still receive the same error form =
Postgres:
style=3D'font-size:
10.0pt'>> org.postgresql.util.PSQLException: ERROR: out of shared =
memory
style=3D'font-size:
10.0pt'>> Is this message appropriate to the real cause of the =
problem or
the
style=3D'font-size:
10.0pt'>> reason of the failure is actually other than what is =
displayed in
this
style=3D'font-size:
10.0pt'>> message?
style=3D'font-size:
10.0pt'>>
style=3D'font-size:
10.0pt'>Maybe you've got an application that is doing a BEGIN WORK, but =
never
style=3D'font-size:
10.0pt'>doing a rollback or commit?
style=3D'font-size:
10.0pt'>--
style=3D'font-size:
10.0pt'>Adam Tauno Williams, Network & Systems =
Administrator
style=3D'font-size:
10.0pt'>Consultant - =
http://www.whitemiceconsulting.com
style=3D'font-size:
10.0pt'>Developer - =
http://www.opengroupware.org
style=3D'font-size:
10.0pt'>
style=3D'font-size:
10.0pt'>
style=3D'font-size:
10.0pt'>---------------------------(end of
broadcast)---------------------------
style=3D'font-size:
10.0pt'>TIP 9: In versions below 8.0, the planner will ignore your =
desire to
style=3D'font-size:
10.0pt'> choose an index scan if =
your joining column's datatypes do not
style=3D'font-size:
10.0pt'> =
match