On Wed, Jan 15, 2014 at 6:07 PM, Tirthankar Barari wrote:
> My tables are:
>
> table test_metric (
> id varchar(255) not null, // just auto generated uuid from app
> timestamp timestamp not null,
> version int4,
> entity_id varchar(255) not null,
> primary k
On 01/13/2014 01:38 PM, Francisco Olarte wrote:
Hi:
On Mon, Jan 13, 2014 at 5:26 PM, Tirthankar Barari wrote:
On 01/10/2014 07:06 AM, Francisco Olarte wrote:
Not related to your vacuum problem, but if your pattern is something
like deleting everything inserted 15 days ago you may want to thin
On 01/10/2014 07:06 AM, Francisco Olarte wrote:
Hi:
On Thu, Jan 9, 2014 at 7:50 PM, Tirthankar Barari wrote:
We have a table where we insert about 10 million rows everyday. We keep 14
day's worth of entries (i.e. 140 mil). A scheduled task wakes up every day
and deletes all entries past the 14
Hi:
On Mon, Jan 13, 2014 at 5:26 PM, Tirthankar Barari wrote:
> On 01/10/2014 07:06 AM, Francisco Olarte wrote:
>> Not related to your vacuum problem, but if your pattern is something
>> like deleting everything inserted 15 days ago you may want to think of
>> using partitioning or simple inherit
On Fri, 10 Jan 2014 13:06:21 +0100 Francisco Olarte
wrote:
> Hi:
>
> On Thu, Jan 9, 2014 at 7:50 PM, Tirthankar Barari wrote:
> > We have a table where we insert about 10 million rows everyday. We keep 14
> > day's worth of entries (i.e. 140 mil). A scheduled task wakes up every day
> > and del
Hi:
On Thu, Jan 9, 2014 at 7:50 PM, Tirthankar Barari wrote:
> We have a table where we insert about 10 million rows everyday. We keep 14
> day's worth of entries (i.e. 140 mil). A scheduled task wakes up every day
> and deletes all entries past the 14 day window (i.e. deletes entries from
> the
Tirthankar Barari writes:
> However, we are noticing that after autovacuum, our disk space
> consumption is still increasing and the increase is in the index size
> (by querying pg_total_relation_size("mytable") and
> pg_indexes_size("mytable")).
> In Postgres 9.2.2, doesn't autovacuum cleanup
