On Fri, Feb 1, 2013 at 2:40 PM, Pavan Deolasee wrote:
>
>
> On Fri, Feb 1, 2013 at 5:19 PM, Vlad Bailescu wrote:
>
>>
>>
>> Pavan, it seems there's a small issue with copy-paste and column
>> text-align. Table sizes are:
>>
>> 4136 kB 2448 kB 2336 kB
>
>
> Ah OK. I see.
>
>
>>
>> 2012-12-05 00
Vlad Bailescu wrote:
> Because of our application stack (Hibernate ORM) we use a
> before_insert trigger to insert rows into the right partition and
> in the master table and then an after_insert trigger to delete
> them from master table (we need the original insert to return the
> inserted row
On Fri, Feb 1, 2013 at 5:19 PM, Vlad Bailescu wrote:
>
>
> Pavan, it seems there's a small issue with copy-paste and column
> text-align. Table sizes are:
>
> 4136 kB 2448 kB 2336 kB
Ah OK. I see.
>
> 2012-12-05 00:44:23 EET LOG: automatic analyze of table
> "fleet.fleet.vehicle_position"
On Fri, Feb 1, 2013 at 1:08 PM, Pavan Deolasee wrote:
>
>
> On Fri, Feb 1, 2013 at 3:24 PM, Vlad Bailescu wrote:
>
>>
>>
>> Stats show only 3 tables get frequently autovacuumed
>>
>> Table Name Tuples inserted Tuples updated Tuples deleted Tuples HOT
>> updated Live Tuples Dead Tuples Last vac
On Fri, Feb 1, 2013 at 3:24 PM, Vlad Bailescu wrote:
>
>
> Stats show only 3 tables get frequently autovacuumed
>
> Table Name Tuples inserted Tuples updated Tuples deleted Tuples HOT
> updated Live Tuples Dead Tuples Last vacuum Last autovacuum Last analyze Last
> autoanalyze Vacuum counter A
On Fri, Feb 1, 2013 at 11:01 AM, Pavan Deolasee wrote:
>
> Do you know for sure that its the master table that generating all the
> vacuum traffic ? What about the partition tables ? Do they get any
> updates/deletes ? It might be useful if you could turn autovacuum
> logging ON and see which tabl
On Fri, Feb 1, 2013 at 1:44 PM, Vlad Bailescu wrote:
> Hi everyone,
>
> We are experiencing a strange situation after upgrading our Postgres from
> 8.4 to 9.1 and our OS from Debian 6 to Ubuntu 12.04 LTS.
>
> We have an application where we are collecting timestamp-based data. Since a
> month of d
Hi everyone,
We are experiencing a strange situation after upgrading our Postgres from
8.4 to 9.1 and our OS from Debian 6 to Ubuntu 12.04 LTS.
We have an application where we are collecting timestamp-based data. Since
a month of data goes over 30M rows (and growing each month), we decided to
par
