Folks, Please help us resolve a discussion on -hackers.
PostgreSQL 9.1 is likely to have, as a feature, the ability to create tables which are "unlogged", meaning that they are not added to the transaction log, and will be truncated (emptied) on database restart. Such tables are intended for highly volatile, but not very valuable, data, such as session statues, application logs, etc. The question is, how would you, as a DBA, expect pg_dump backups to treat unlogged tables? Backing them up by default has the potential to both cause performance drag on the unlogged table and make your backups take longer unless you remember to omit them. Not backing them up by default has the drawback that if you forget --include-unlogged switch, and shut the database down, any unlogged data is gone. How would you *expect* unlogged tables to behave? Survey is here: https://spreadsheets.google.com/ccc?key=0AoeuP3g2YZsFdDFnT2VKNC1FQ0pQNmJGS2dWMTNYMEE&hl=en&authkey=CISbwuYD -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
