From: | MindTerm <mindterm(at)yahoo(dot)com> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: performance tuning in large function / transaction |
Date: | 2001-12-14 03:34:28 |
Message-ID: | 20011214033428.93468.qmail@web20203.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi all,
I will try to assign more memory to shared memory,
say 50M ~ 100M .
I am runing something like that ..
cursor loop 1
cursor loop 2
cursor loop 3
tmp = primary key
delete tmp ....
insert tmp ....
end loop 3
end loop 2
end loop 3
will delete and insert record with same primary key
within a transaction reduce the performance ?
M.T.
--- Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
wrote:
> On Thu, 13 Dec 2001, MindTerm wrote:
>
> > I am writing a function (plpgsql) which equals
> to a
> > single transaction transaction in postgresql ( as
> I
> > known ). So I think that it is not a autocommmit
> mode.
> >
> > I have add following lines in postgresql.conf.
> >
> > postgresql.conf:
> > ====================
> > shared_buffers = 640
> > wal_buffers = 80
>
> It depends on how much memory you have, but even 640
> is pretty
> low (I think that works out to 5M). Probably a few
> thousand
> is better if you've got the ram.
>
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2001-12-14 03:43:59 | Re: performance tuning in large function / transaction |
Previous Message | Stephan Szabo | 2001-12-14 03:02:05 | Re: performance tuning in large function / transaction |