How about enable/disable triggers? >From TODO: > Allow triggers to be disabled.
http://momjian.postgresql.org/cgi-bin/pgtodo?trigger I think this is good for COPY performance improvement. Now I have user functions to enable/disable triggers, not DDL. It modifies system tables. But I can rewrite this as a DDL. (ALTER TABLE?) Any comments? Bruce Momjian wrote: > Here are our open items. How hard are we going to be about the cutoff > date? Do we give people the weekend to complete some items? > > --------------------------------------------------------------------------- > > > PostgreSQL 8.1 Open Items > ========================= > > Current version at http://candle.pha.pa.us/cgi-bin/pgopenitems. > > Changes > ------- > integrated auto-vacuum (Alvaro) > ICU locale patch? > Win32 signal handling patch (Magnus) > column-level triggers (Greg) > interval improvements (Michael Glaesemann) > move rtree_gist into core? > config file I/O? (Adreas) > terminate backend fix? > dbsize functions from /contrib? (Andreas) > fix pg_autovacuum O(n^2) behavior > remove wal siblings guc vars? > COPY performance improvements (greenplum) > shared dependency (Alvaro) > concurrent vacuum (Hannu) > make pg_dump E''escape safe > table partitionaing (Simon) > WAL improvements (Simon) > > Documentation > ------------- > > Fixed Since Last Beta > --------------------- > -- NAGAYASU Satoshi <[EMAIL PROTECTED]> ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
