From e19d10b595f2ac6aaa4be158163b44d8975898d2 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 29 May 2008 02:04:15 +0000 Subject: Add description to: * Add deferred trigger queue file < This item involves dumping large queues into files. > This item involves dumping large queues into files, or doing some > kind of join to process all the triggers, or some bulk operation. --- doc/src/FAQ/TODO.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 864051abaf..607509d82b 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Wed May 28 21:58:24 EDT 2008 +Last updated: Wed May 28 22:04:08 EDT 2008

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -1057,7 +1057,8 @@ first. There is also a developer's wiki at

  • Add deferred trigger queue file

    Right now all deferred trigger information is stored in backend memory. This could exhaust memory for very large trigger queues. - This item involves dumping large queues into files. + This item involves dumping large queues into files, or doing some + kind of join to process all the triggers, or some bulk operation. http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php

  • Allow triggers to be disabled in only the current session. -- cgit v1.2.3