Excerpts from Robert Haas's message of sáb dic 18 02:21:41 -0300 2010: > Here's an attempt to summarize the remaining issues with this patch > that I know about. I may have forgotten something, so please mention > it if you notice something missing. > > 1. pg_dump needs an option to control whether unlogged tables are > dumped. --no-unlogged-tables seems like the obvious choice, assuming > we want the default to be to dump them, which seems like the safest > option.
If there are valid use cases for some unlogged tables being dumped and some others not, would it make sense to be able to specify a pattern of tables to be dumped or skipped? -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
