From d9bc39a7046fcf711b676de02c28475d9102a4ad Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 24 Mar 2008 14:17:06 +0000 Subject: Update wording: < o Allow pre/data/post files when dumping a single object, for < performance reasons > o Allow pre/data/post files when schema and data are dumped > separately, for performance reasons --- doc/src/FAQ/TODO.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 63bd5374815..8c9c3d5085b 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: Sun Mar 23 08:36:50 EDT 2008 +Last updated: Mon Mar 24 10:16:57 EDT 2008

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

Using psql to restore a pg_dump dump is also affected.

Remove pre-7.3 pg_dump code that assumes pg_depend does not exit -

Allow pre/data/post files when dumping a single object, for - performance reasons +

Allow pre/data/post files when schema and data are dumped + separately, for performance reasons

http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php

-- cgit v1.2.3