| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | paladine <yasinmalli(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump-restore concurrency |
| Date: | 2010-07-21 12:02:21 |
| Message-ID: | 4C46E1CD.4000303@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 21/07/10 19:26, paladine wrote:
>
> Hi all
> I prefer doing pg_dump - psql restore to vacuum full and
> is there anyone know whether postgresql can insert data concurrently while
> restoring a table for not losing any data.
There's no particular reason why you can't just feed a data-only dump
into psql. It should copy all that data into the table without affecting
new inserts.
If you're doing anything more complex, messing with many tables at once
etc, then just use the commands built in to PostgreSQL for the purpose.
If you don't like VACUUM FULL for some reason, you should fix your
autovacuuming so that you don't need it.
See the postgresql documentation and the wiki entries on VACUUM FULL,
autovacuum, etc.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | paladine | 2010-07-21 12:21:04 | Re: pg_dump-restore concurrency |
| Previous Message | paladine | 2010-07-21 11:26:28 | pg_dump-restore concurrency |