| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Francisco Reyes <lists(at)stringsutils(dot)com> |
| Cc: | John Smith <sodgodofall(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Backup/Restore of single table in multi TB database |
| Date: | 2008-07-19 09:02:32 |
| Message-ID: | 1216458152.19656.799.camel@ebony.2ndQuadrant |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Fri, 2008-07-18 at 20:25 -0400, Francisco Reyes wrote:
> Does pg_snapclone works mostly on large rows or will it also be faster
> than pg_dump for narrow tables?
It allows you to run your dump in multiple pieces. Thats got nothing to
do with narrow or wide.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2008-07-19 11:22:01 | Re: Reducing memory usage of insert into select operations? |
| Previous Message | Stefan Kaltenbrunner | 2008-07-19 07:15:51 | Re: Initdb problem on debian mips cobalt: Bus error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephane Bailliez | 2008-07-19 13:19:43 | Performance on Sun Fire X4150 x64 (dd, bonnie++, pgbench) |
| Previous Message | Francisco Reyes | 2008-07-19 01:45:07 | Re: An "obvious" index not being used |