| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: no XLOG during COPY? |
| Date: | 2008-09-15 10:59:40 |
| Message-ID: | 1221476380.3913.1277.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2008-09-11 at 15:25 -0400, Andrew Dunstan wrote:
> Great, thanks (and also to Guillaume).
>
> It looks to me like the simple way around this issue would be to provide
> an option to have pg_restore emit:
> begin; truncate foo; copy foo ... commit;
>
> The truncate will be trivial as there won't be any data or indexes at
> that stage anyway.
Not sure which stage you're talking about. If this is a parallel restore
and you are running a create in one session and a load in another, then
ISTM you have no way of knowing that for certain.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-15 11:04:01 | Re: Transaction Snapshots and Hot Standby |
| Previous Message | Devrim GÜNDÜZ | 2008-09-15 10:21:08 | New shapshot RPMs (Sep 15 2008) are ready for testing |