| From: | Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com> |
|---|---|
| To: | Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: update functions locking tables |
| Date: | 2005-08-30 16:00:18 |
| Message-ID: | a595de7a05083009006016da49@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2005/8/30, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>:
> On Tue, Aug 30, 2005 at 10:18:20AM -0300, Clodoaldo Pinto wrote:
> > A vacuum full or a cluster is totally out of reach since each take
> > about one hour.
>
> Even if you cluster/vacuum only the just-loaded table?
>
No, that would be much faster. The biggest just updated is about 600
thousand rows. I will consider it.
> > The biggest table is 170 million rows long.
>
> I hope this is not the one you are loading daily ...
>
I load daily 8 times 700+ thousand rows.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-08-30 16:07:24 | Re: detection of VACUUM in progress |
| Previous Message | Tom Lane | 2005-08-30 15:53:56 | Re: detection of VACUUM in progress |