| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Norberto Delle <betodelle(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum and pg_largeobject |
| Date: | 2010-07-02 16:57:22 |
| Message-ID: | 1278089733-sup-1860@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Excerpts from Norberto Delle's message of vie jul 02 08:10:44 -0400 2010:
> Hi all
>
> I would like to know if the large object table pg_largeobject is
> routinely checked by the autovacuum daemon.
> I ask about this because I have a database in wich the pg_largeobject
> table is being forcibly vacuumed because it's relfrozenxid is now
> greater than autovacuum_freeze_max_age, and it's killing the server
> performance. PostgreSQL version is 8.2.14.
It should, as it should vacuum any other table. Perhaps all the routine
autovacuums were killed because of locking issues. I admit I haven't
investigated the locking behavior of pg_largeobject in particular.
Would it be locked more frequently than other system catalogs?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Babu R | 2010-07-02 17:28:23 | Re: bulk insert using COPY and PHP code |
| Previous Message | Tim | 2010-07-02 16:22:45 | ERROR: canceling statement due to statement timeout |