Re: BUG #7521: Cannot disable WAL log while using pg_dump

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: BUG #7521: Cannot disable WAL log while using pg_dump
Дата
Msg-id CABOikdOQx0gZ=_7aV7tVgN=PsgcmqeOuzB6pP2Q9XkLcv9Aj-Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #7521: Cannot disable WAL log while using pg_dump  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: BUG #7521: Cannot disable WAL log while using pg_dump  (Gezeala M. Bacuño II <gezeala@gmail.com>)
Список pgsql-bugs
On Fri, Sep 7, 2012 at 2:43 AM, Alvaro Herrera <alvherre@2ndquadrant.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #7516: PL/Perl crash
Следующее
От: iradu@unix-world.org
Дата:
Сообщение: BUG #7522: ecpg build error