On 11/16/2010 07:25 PM, Tom Lane wrote:
Man, the number of misunderstandings in this thread is staggering....
First, I have plenty of processes that I would immediately convert to using this (and, FWIW, none of them would benefit from preserving data across restarts). But I have some questions that may expose my misunderstandings:
1. Would there be restrictions preventing a standard table from having a FK or other constraint that depends on an unlogged table? If not, it seems like there could be an unwanted ripple-effect from lost of the unlogged table.
2. Would it be possible to accidentally mix logged and unlogged tables in an inheritance chain? What would be the impact?
3. If unlogged data is included in a dump (my vote is no), would this lead to inconsistent behavior between dumps taken from a master and dumps taken from a hot-standby?
4. Would it be reasonable for temporary-tables to be unlogged by default? Cheers, Steve -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
