From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
Cc: | Gregory Haase <haaseg(at)onefreevoice(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: json datatype and table bloat? |
Date: | 2013-10-29 14:06:22 |
Message-ID: | CAHyXU0yp9w1vgZcrc41kqq3o-6tqSVCmssBgFkt4vJAK6gZXSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Oct 29, 2013 at 5:38 AM, Chris Travers <chris(dot)travers(at)gmail(dot)com> wrote:
>
>
>
> On Mon, Oct 28, 2013 at 4:17 PM, Gregory Haase <haaseg(at)onefreevoice(dot)com>
> wrote:
>>
>> I have a table that is triggering my nagios database bloat alert
>> regularly. Usually, I have to give it the vacuum full more than once to get
>> it under the threshold. Today I tried repeatedly and cannot get the alert to
>> resolve.
>>
>> I had a discussion with one of the primary developers about how the table
>> is utilized, and it turns out they are basically only ever inserting into
>> it. This sort of flies in the face of conventional wisdom about bloat being
>> caused by frequent updates and deletes.
>
>
> As I understand it, vacuuming only removes the tuples removed by delete and
> update operations.
well, or by rolled back transactions. we we have to wonder if OP has
a lot of queries trying to insert and failing. maybe check the log?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Matt | 2013-10-29 14:37:36 | Re: INSERT/UPDATE statements sometimes choosing not to use PK index? |
Previous Message | Tom Lane | 2013-10-29 13:45:11 | Re: INSERT/UPDATE statements sometimes choosing not to use PK index? |