pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dawn Hollingsworth <dmh@airdefense.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres Connections Requiring Large Amounts of Memory
Date: 16 Jun 2003 08:57:35 +0000
Message-ID: <1055753856.5467.57.camel@kaos> (raw)
In-Reply-To: <6634.1055796302@sss.pgh.pa.us>
References: <1055752337.2182.49.camel@kaos>
	<6634.1055796302@sss.pgh.pa.us>


We have just recently hired a database consultant familiar with Postgres
and just on his cursory glance we are not doing anything really crazy.

There are two things which might be considered off the beaten path
though:

1. We have tables that have over 500 columns which we continually insert
into and select from.

2. Our stored procedures take more than 16 parameters so in the file
config.h the value INDEX_MAX_KEYS was increased to 100.

-Dawn

On Mon, 2003-06-16 at 20:45, Tom Lane wrote:
> Dawn Hollingsworth <dmh@airdefense.net> writes:
> > PostgreSQL Version: 7.2.3
> 
> > My problem is that the memory used by the connections appears to grow
> > over time, especially when the amount of data entering the system is
> > increased.
> 
> We have fixed memory-leak problems in the past, and I wouldn't be
> surprised if some remain, but you'll have to give a lot more detail
> about what you're doing if you want help.  A leak that persists across
> transaction boundaries is fairly surprising --- I think I can safely
> say that there are none in the normal code paths.  I'm guessing you must
> be using some off-the-beaten-path feature.
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings





view thread (11+ messages)  latest in thread

Message-ID: <1055753856.5467.57.camel@kaos>
Permalink:  ../1055753856.5467.57.camel@kaos/
Also on:    postgresql.org/message-id/1055753856.5467.57.camel@kaos

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: dmh@airdefense.net, tgl@sss.pgh.pa.us
  Subject: Re: Postgres Connections Requiring Large Amounts of Memory
  In-Reply-To: <1055753856.5467.57.camel@kaos>
  References: <1055752337.2182.49.camel@kaos> <6634.1055796302@sss.pgh.pa.us> <1055753856.5467.57.camel@kaos>

* 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