| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Boy de Laat <boy(at)atsc(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
| Date: | 2012-09-07 03:48:57 |
| Message-ID: | CABOikdOQx0gZ=_7aV7tVgN=PsgcmqeOuzB6pP2Q9XkLcv9Aj-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Fri, Sep 7, 2012 at 2:43 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>wrote:
> Excerpts from Boy de Laat's message of jue sep 06 17:24:35 -0300 2012:
> >
> > At the time my backup starts i see much WAL logs being generated?
>
> I guess we'd need to see what the generated WAL logs are, either with
> xlogdump or XLOG_DEBUG turned on ...
>
>
Can a long running pg_dump transaction have some ill effect on the amount
of WAL generation ? It can definitely cause unusual additional bloat if the
database is being continuously updated during that period, but not sure it
can cause additional WAL.
OP probably needs to tell us whats the size of the database, how's the
access pattern, how long does it take to dump the entire database and how
many more WAL files generated during this process compared to average rate.
Thanks,
Pavan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-07 04:59:18 | Re: BUG #7522: ecpg build error |
| Previous Message | Tom Lane | 2012-09-06 23:03:05 | Re: BUG #7516: PL/Perl crash |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2012-09-07 04:52:46 | pg_dump transaction's read-only mode |
| Previous Message | Tom Lane | 2012-09-07 02:54:25 | Re: 9.2rc1 produces incorrect results |