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, Ben Scherrey <scherrey@proteus-tech.com>
Subject: Re: Postgres Connections Requiring Large Amounts of Memory
Date: 17 Jun 2003 11:03:28 +0000
Message-ID: <1055847810.2833.260.camel@kaos> (raw)
In-Reply-To: <15851.1055887425@sss.pgh.pa.us>
References: <1055752337.2182.49.camel@kaos>
	<6634.1055796302@sss.pgh.pa.us>
	<1055753856.5467.57.camel@kaos>
	<6892.1055799269@sss.pgh.pa.us>
	<1055832411.5467.100.camel@kaos>
	<14875.1055878682@sss.pgh.pa.us>
	<1055842927.2182.227.camel@kaos>
	<15851.1055887425@sss.pgh.pa.us>


Each stored procedure only updates one row and inserts one row. 

I just connected the user interface to the database. It only does
selects on startup. It's connection jumped to a memory usage of 256M. 
It's not getting any larger but it's not getting any smaller either.

I'm going to compile postgres with the SHOW_MEMORY_STATS. I'm assuming I
can just set ShowStats equal to 1. I'll also pare down the application
to only use one of the stored procedures for less noise and maybe I can
track where memory might be going. And in the meantime I'll get a test
going with Postgres 7.3 to see if I get the same behavior.

Any other suggestions?

-Dawn

On Tue, 2003-06-17 at 22:03, Tom Lane wrote:


> The only theory I can come up with is that the deferred trigger list is
> getting out of hand.  Since you have foreign keys in all the tables,
> each insert or update is going to add a trigger event to the list of
> stuff to check at commit.  The event entries aren't real large but they
> could add up if you insert or update a lot of stuff in a single
> transaction.  How many rows do you process per transaction?
> 
> 			regards, tom lane

view thread (11+ messages)  latest in thread

Message-ID: <1055847810.2833.260.camel@kaos>
Permalink:  ../1055847810.2833.260.camel@kaos/
Also on:    postgresql.org/message-id/1055847810.2833.260.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, scherrey@proteus-tech.com
  Subject: Re: Postgres Connections Requiring Large Amounts of Memory
  In-Reply-To: <1055847810.2833.260.camel@kaos>
  References: <1055752337.2182.49.camel@kaos> <6634.1055796302@sss.pgh.pa.us> <1055753856.5467.57.camel@kaos> <6892.1055799269@sss.pgh.pa.us> <1055832411.5467.100.camel@kaos> <14875.1055878682@sss.pgh.pa.us> <1055842927.2182.227.camel@kaos> <15851.1055887425@sss.pgh.pa.us> <1055847810.2833.260.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