| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, alexk <alexk(at)commandprompt(dot)com>, Alexander Shulgin <ash(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postmaster holding unlinked files for pg_largeobject table |
| Date: | 2011-06-06 16:17:10 |
| Message-ID: | 1307376945-sup-7246@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Excerpts from Tom Lane's message of lun jun 06 12:10:24 -0400 2011:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Hmm interesting. I don't think the placement suggested by Tom would be
> > useful, because the Zabbix backends are particularly busy all the time,
> > so they wouldn't run ProcessCatchupEvent at all.
>
> Yeah, I wasn't that thrilled with the suggestion either. But we can't
> just have backends constantly closing every open FD they hold, or
> performance will suffer. I don't see any very good place to do this...
How about doing something on an sinval message for pg_database?
That doesn't solve the WAL problem Kevin found, of course ...
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tarabas | 2011-06-06 16:20:04 | Non returning Transactions/Many Locks in Postgres 9.0.4 and 9.0.1 |
| Previous Message | Tom Lane | 2011-06-06 16:10:24 | Re: Postmaster holding unlinked files for pg_largeobject table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2011-06-06 16:18:14 | Re: Range Types and extensions |
| Previous Message | Simon Riggs | 2011-06-06 16:15:28 | WALInsertLock tuning |