Re: Commit within a PL/PGSQL procedure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Harry Broomhall" <harry(dot)broomhall(at)uk(dot)easynet(dot)net>
Cc: josh(at)agliodbs(dot)com (Josh Berkus), pgsql-novice(at)postgresql(dot)org
Subject: Re: Commit within a PL/PGSQL procedure
Date: 2003-06-17 21:49:36
Message-ID: 15748.1055886576@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Harry Broomhall <harry(dot)broomhall(at)uk(dot)easynet(dot)net> writes:
> In fact my *test* function consists of a simple scan through a database,
> and 3 INSERTs into a new table for each record in the original, where
> the values inserted are derived from values in the original.
> The source file is about 6.4 ^6 records, and the system dies at about
> the 1 million mark.

Now that I think twice, do you have foreign key linkages in the
tables being inserted into? If so, the most likely explanation is just
that the list of deferred trigger events is getting too large. This is
a known deficiency on our TODO list (it should be possible to shove the
list out to disk when it gets too large).

regards, tom lane

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Shmuel A. Kahn 2003-06-17 22:06:01 Can't get postmaster to start :-(
Previous Message Lynna Landstreet 2003-06-17 20:13:28 Re: Multibyte support and accented characters