From: | Harry Broomhall <harry(dot)broomhall(at)uk(dot)easynet(dot)net> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | harry(dot)broomhall(at)uk(dot)easynet(dot)net, josh(at)agliodbs(dot)com, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Commit within a PL/PGSQL procedure |
Date: | 2003-06-18 08:59:55 |
Message-ID: | 200306180859.JAA64042@haeb.noc.uk.easynet.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Tom Lane writes:
> 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?
Spot on! The new table has a field that references an ID in the
original table.
> 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).
Any way round this?
Regards,
Harry.
From | Date | Subject | |
---|---|---|---|
Next Message | Mel Jamero | 2003-06-18 12:38:17 | sql question (hopefully) |
Previous Message | Smitha V. Babu | 2003-06-18 08:58:25 | help:steps needed to get the content of table from the database.. . |