On Thu, 11 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
'k, does this help any?
TopMemoryContext: 40960 total in 4 blocks; 8632 free (10 chunks); 32328 used
SPI Plan: 3072 total in 2 blocks; 1728 free (0 chunks); 1344 used
TopTransactionContext: 534765568 total in 74 blocks; 2144 free (68 chunks);
534763424 used
Yeah, the leak is clearly in TopTransactionContext. That doesn't let
the trigger code off the hook though, because the pending-triggers list
is kept there. Are you *sure* there are no AFTER triggers here?
(Don't forget foreign-key checking triggers.)
This is all of them ... nothing AFTER, just ON or BEFORE ...
Foreign-key constraints:
"xa_classification_id_fk" FOREIGN KEY (classification_id) REFERENCES
xa_classification(classification_id) ON UPDATE RESTRICT ON DELETE RESTRICT
"xa_ip_address_id_fk" FOREIGN KEY (ip_address_id) REFERENCES
xa_ip_addresses(ip_address_id) ON UPDATE RESTRICT ON DELETE RESTRICT
"xa_logger_status_id_fk" FOREIGN KEY (logger_status_id) REFERENCES
xa_logger_status(logger_status_id) ON UPDATE RESTRICT ON DELETE RESTRICT
"xa_url_queue_id_fk" FOREIGN KEY (url_queue_id) REFERENCES
xa_url_queue(url_queue_id) ON UPDATE RESTRICT ON DELETE SET NULL
Triggers:
xa_url_domain_b_i_u BEFORE INSERT OR UPDATE ON xa_url FOR EACH ROW EXECUTE
PROCEDURE xa_url_domain()
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
