On Fri, Jul 25, 2008 at 11:17:20PM +0100, Gregory Stark wrote: > "Joshua D. Drake" <[EMAIL PROTECTED]> writes: > > > How do we deal with this? > > > > pg_dump -w "last_update_timestamp < ..." -t 'table*' > > > > What I see is a recipe for inconsistent, un-restorable backups without a > > user realizing what they have done. The only way to deal with the above > > is: > > > > 1. Wildcards aren't allowed if you have -w > > 2. You dump everything, if the WHERE clause isn't relevant you just dump > > the whole table > > There's always > > 3. Apply the WHERE clause to all tables and if there's a table missing > columns referenced in the where clause then fail with the appropriate > error. > > Which seems like the right option to me. The tricky bit would be how to deal > with cases where you want a different where clause for different tables. But > even if it doesn't handle all cases that doesn't mean a partial solution is > unreasonable.
Actually, Davy's patch does deal with the case "where you want a different where clause for different tables". -dg -- David Gould [EMAIL PROTECTED] 510 536 1443 510 282 0869 If simplicity worked, the world would be overrun with insects. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
