| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Svetlin Manavski <svetlin(dot)manavski(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Join over two tables of 50K records takes 2 hours |
| Date: | 2011-10-14 09:41:34 |
| Message-ID: | CAOR=d=3kdC9QcwJt5a1rdJZWRqeuVKWkAp6xX6Pt-t-khACsyA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Oct 14, 2011 at 2:35 AM, Svetlin Manavski
<svetlin(dot)manavski(at)gmail(dot)com> wrote:
> Thank you guys for spotting the problem immediately.
> The reason for such autovacuum thresholds is that these tables are designed
> for very high rate of inserts and I have a specific routine to analyze them
> in a more controlled way. Infact the stats target of some of the fields is
> also high. However that routine was failing to perform analyze on
> appqosdata.icmptraffic and its children due to another issue...
Note that it's possible to set many of the autovacuum values per table
so you don't have to do a brainyectomy on the whole autovac system.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arjen van der Meijden | 2011-10-14 10:41:34 | Re: SSD options, small database, ZFS |
| Previous Message | Svetlin Manavski | 2011-10-14 08:35:57 | Re: Join over two tables of 50K records takes 2 hours |