Re: BUG #10155: BUG? Cann't remove new generated tuples after repeatable read transaction start.

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: 德哥 <digoal(at)126(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #10155: BUG? Cann't remove new generated tuples after repeatable read transaction start.
Date: 2014-04-29 06:55:00
Message-ID: 535F4CC4.5040806@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 04/29/2014 02:18 AM, 德哥 wrote:
> HI,
> This is so bad in pg_dump use, when a database so big.
> because pg_dump is also use repeatable read isolation. and when pg_dump backup database , the database will bloat .

Yep. One approach is to take a filesystem-level backup (ie. with
pg_start/stop_backup() or pg_basebackup), start a second server from
that backup, and run pg_dump against that.

> Can we optimize it?

Not easily. I'd love to do something about it, but it's going to be a
long project.

- Heikki

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2014-04-29 07:23:58 Re: BUG #10142: Downstream standby indefinitely waits for an old WAL log in new timeline on WAL Cascading replicatio
Previous Message 德哥 2014-04-28 23:18:48 Re: BUG #10155: BUG? Cann't remove new generated tuples after repeatable read transaction start.