| From: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | "Bill Moran" <wmoran(at)collaborativefusion(dot)com> |
| Cc: | "PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Dumping/Restoring with constraints? |
| Date: | 2008-08-27 14:40:41 |
| Message-ID: | e373d31e0808270740u38873cccx32b24796f02438e6@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Wed, Aug 27, 2008 at 10:34 PM, Bill Moran
<wmoran(at)collaborativefusion(dot)com> wrote:
>>
>>
>> Dumb question. Will this kind of pg_dumpall lead to downtime, I mean
>> is there a database lock during this time?
>
> No.
Thanks. But there seems to be a tangible slowdown of DB operations
during the time that pg_dump is running. Perhaps some of my
postgresql.conf variables are not geared to this. (I vaguely recall
setting it up so that the wal_buffers or checkpoint_segments needed to
be set upwards for maintenance tasks).
My question: is it possible to interactively set up these variables so
that pg_dumpall can work very fast? And behind the scenes, without
slowing stuff down?
Thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-27 14:42:56 | Re: Dumping/Restoring with constraints? |
| Previous Message | Bill Moran | 2008-08-27 14:34:29 | Re: Dumping/Restoring with constraints? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-27 14:42:56 | Re: Dumping/Restoring with constraints? |
| Previous Message | Bill Moran | 2008-08-27 14:34:29 | Re: Dumping/Restoring with constraints? |