Re: pg_dump's results have quite different size

From: Kaijiang Chen <chenkaijiang(at)gmail(dot)com>
To: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_dump's results have quite different size
Date: 2016-12-14 05:00:53
Message-ID: CAAkGvS-qnQ8ZGJ0C-ttiym6QVpHyDogZa=_fPdUbSyKrt85zPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I found that it is because I run the pg_dump on standby and it conflicts
with the stream replication. I enlarge the max_standby_streaming_delay. It
should work.

On Fri, Dec 9, 2016 at 12:27 PM, Kaijiang Chen <chenkaijiang(at)gmail(dot)com>
wrote:

> Hi, I have postgresql 9.4.10, CentOS 6.5, 64 bit. I got the source codes,
> built and gmake install.
>
> I pg_dump the database 3 times everyday. The weird thing is that the sizes
> of the dump files are sometimes quite different.
>
> For example, the file dumped in 7am is 1.5G and the file dumped in 11am is
> 0.91G -- about 60% gap! But no massive deletion happened. Only some
> insertion/updating (less than 10K) in between 2 dump operations. Un-logical
> to have different sizes.
>
> Note that in about 70% cases, file sizes are similar to each other and
> keeps increasing a little bit, which is very logical. But sometimes I got
> weird things as described above.
>
> Is that a bug? Or something else?
>
> Regards,
> Kaijiang
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2016-12-14 06:54:32 BUG #14466: can with recursive query add LOOPth variable?
Previous Message David G. Johnston 2016-12-14 03:57:00 Re: BUG #14465: cursor for insert into select ... returning cann't streaming fetch?