| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Visibility Groups |
| Date: | 2008-08-07 16:44:00 |
| Message-ID: | 87prokixm7.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Alvaro Herrera" <alvherre(at)commandprompt(dot)com> writes:
> Gregory Stark wrote:
>
>> I think Simon's interface was overly complex but if we can simplify it then it
>> could be useful. As Grittner mentioned implicit queries could make use of it
>> automatically. Also pg_dump or Slony could make use of it automatically.
>
> Hmm, what use would it have for pg_dump? Normally, when it is a
> problem, you want access to a large set of tables, frequently all of
> them.
Well pg_dump -t or pg_restore -L
For that matter pg_restore generally knows it's not going to access any
existing tables that don't match the tables it's restoring...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Asko Oja | 2008-08-07 16:47:16 | Re: Avoiding Application Re-test |
| Previous Message | Simon Riggs | 2008-08-07 16:26:18 | Re: Visibility Groups |