pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: SZŰCS Gábor <surrano@mailbox.hu>
To: pgsql-performance@postgresql.org
Subject: Re: Postgres Connections Requiring Large Amounts of Memory
Date: Wed, 18 Jun 2003 09:11:25 +0200
Message-ID: <004a01c33568$d48235c0$0403a8c0@fejleszt4> (raw)
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>

----- Original Message ----- 
From: "Dawn Hollingsworth" <dmh@airdefense.net>
Sent: Tuesday, June 17, 2003 11:42 AM


> I'm not starting any of my own transactions and I'm not calling stored
> procedures from withing stored procedures. The stored procedures do have
> large parameters lists, up to 100. The tables are from 300 to 500

Geez! I don't think it'll help you find the memory leak (if any), but
couldn't you normalize the tables to smaller ones? That may be a pain when
updating (views and rules),  but I think it'd worth in resources (time and
memory, but maybe not disk space). I wonder what is the maximum number of
updated  cols and the minimum correlation between their semantics in a
single transaction (i.e. one func call), since there are "only" 100 params
for a proc.

> columns. 90% of the columns are either INT4 or INT8.  Some of these
> tables are inherited. Could that be causing problems?

Huh. It's still 30-50 columns (a size of a fairly large table for me) of
other types :)

G.
------------------------------- cut here -------------------------------




view thread (11+ messages)

Message-ID: <004a01c33568$d48235c0$0403a8c0@fejleszt4>
Permalink:  ../004a01c33568$d48235c0$0403a8c0@fejleszt4/
Also on:    postgresql.org/message-id/004a01c33568$d48235c0$0403a8c0@fejleszt4

 · 

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: surrano@mailbox.hu
  Subject: Re: Postgres Connections Requiring Large Amounts of Memory
  In-Reply-To: <004a01c33568$d48235c0$0403a8c0@fejleszt4>
  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> <004a01c33568$d48235c0$0403a8c0@fejleszt4>

* 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