Re: PostgreSQL + FreeBSD memory configuration, and an issue

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Gipsz Jakab <clausewitz45(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL + FreeBSD memory configuration, and an issue
Date: 2011-04-08 13:29:52
Message-ID: BANLkTimK75PZTVE4t-sw9BCbtjVYmKLXhw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Apr 8, 2011 at 3:00 AM, Gipsz Jakab <clausewitz45(at)gmail(dot)com> wrote:
> After the settings in the postgresql.conf our system is much faster, and no
> more error messages in the postgres.log, but If I try to drop a table, or
> add a new one, our system is stopping, until I kill the process, which is
> dropping or adding a table.

you are almost certainly waiting on a lock. check pg_locks for
ungranted locks and pg_stat_activity for idle/long running
transactions. If you ever find yourself having to bump
max_connections again, it is almost certainly a good idea to
investigate a connection pooler like pgbouncer.

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2011-04-08 13:33:17 Re: PostgreSQL backend process high memory usage issue
Previous Message salah jubeh 2011-04-08 13:28:47 cast list of oid