pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sorin N. Ciolofan <ciolofan@ics.forth.gr>
Cc: pgsql-general@postgresql.org
Cc: pgsql-admin@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [GENERAL] ERROR: out of shared memory
Date: Tue, 27 Mar 2007 09:59:15 -0400
Message-ID: <19352.1175003955@sss.pgh.pa.us> (raw)
In-Reply-To: <20070327131301.065E38E40FC@mailhost.ics.forth.gr>
References: <20070327131301.065E38E40FC@mailhost.ics.forth.gr>

"Sorin N. Ciolofan" <ciolofan@ics.forth.gr> writes:
> It seems that the legacy application creates tables dynamically and the
> number of the created tables depends on the size of the input of the
> application. For the specific input which generated that error I've
> estimated a number of created tables of about 4000. 
> Could be this the problem?

If you have transactions that touch many of them within one transaction,
then yup, you could be out of locktable space.  Try increasing
max_locks_per_transaction.

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <19352.1175003955@sss.pgh.pa.us>
Permalink:  ../19352.1175003955@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19352.1175003955@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ciolofan@ics.forth.gr, pgsql-general@postgresql.org, pgsql-admin@postgresql.org
  Subject: Re: [GENERAL] ERROR: out of shared memory
  In-Reply-To: <19352.1175003955@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox