On Tue, Jul 4, 2017 at 10:18 PM, Chris Travers wrote:
> First, I haven't seen major problems of database bloat in a long time which
> is why I find this case strange. I wanted to ask here what may be causing
> it.
>
> Problem:
> ==
> Database is in the 100GB to
On Tue, Jul 4, 2017 at 10:18 PM, Chris Travers
wrote:
>
> Questions
> ===
> I assume that it is the fact that rows update frequently which is the
> problem here? But why doesn't Postgres re-use any of the empty disk pages?
>
Can you install the contrib extension
On Wed, Jul 5, 2017 at 3:51 PM, Bill Moran wrote:
> On Wed, 5 Jul 2017 13:28:29 +0200
> Chris Travers wrote:
>
> > On Wed, Jul 5, 2017 at 1:00 PM, PT wrote:
> >
> > > 2x the working size for a frequently updated table
On Wed, 5 Jul 2017 13:28:29 +0200
Chris Travers wrote:
> On Wed, Jul 5, 2017 at 1:00 PM, PT wrote:
>
> > 2x the working size for a frequently updated table isn't terrible bloat.
> > Or are
> > you saying it grows 2x every 24 hours and keeps
On Wed, Jul 5, 2017 at 7:28 AM, Chris Travers
wrote:
>
>
> On Wed, Jul 5, 2017 at 1:00 PM, PT wrote:
>
>>
>> 2x the working size for a frequently updated table isn't terrible bloat.
>> Or are
>> you saying it grows 2x every 24 hours and keeps
On Wed, Jul 5, 2017 at 1:00 PM, PT wrote:
>
> 2x the working size for a frequently updated table isn't terrible bloat.
> Or are
> you saying it grows 2x every 24 hours and keeps growing? The real question
> is
> how often the table is being vacuumed. How long have you
On Wed, 5 Jul 2017 07:18:03 +0200
Chris Travers wrote:
> Hi;
>
> First, I haven't seen major problems of database bloat in a long time which
> is why I find this case strange. I wanted to ask here what may be causing
> it.
>
> Problem:
> ==
> Database is in
On Wed, Jul 5, 2017 at 7:18 AM, Chris Travers
wrote:
> Hi;
>
> First, I haven't seen major problems of database bloat in a long time
> which is why I find this case strange. I wanted to ask here what may be
> causing it.
>
> Problem:
> ==
> Database is in the
Hi;
First, I haven't seen major problems of database bloat in a long time which
is why I find this case strange. I wanted to ask here what may be causing
it.
Problem:
==
Database is in the 100GB to 200GB size range, running on btrfs (not my
choice) with nodatacow enabled (which I set up