Re: Adding WHERE clause to pg_dump
От | Gregory Stark |
---|---|
Тема | Re: Adding WHERE clause to pg_dump |
Дата | |
Msg-id | 87iquthamn.fsf@oxford.xeocode.com обсуждение исходный текст |
Ответ на | Re: Adding WHERE clause to pg_dump ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: Adding WHERE clause to pg_dump
|
Список | pgsql-hackers |
"Joshua D. Drake" <jd@commandprompt.com> 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 failwith 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. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning
В списке pgsql-hackers по дате отправления: