Re: Postmaster holding unlinked files for pg_largeobject table - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Postmaster holding unlinked files for pg_largeobject table
Date
Msg-id 1307555359-sup-5257@alvh.no-ip.org
Whole thread Raw
In response to Re: Postmaster holding unlinked files for pg_largeobject table  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postmaster holding unlinked files for pg_largeobject table
List pgsql-hackers
Excerpts from Tom Lane's message of mar jun 07 12:26:34 -0400 2011:

> It's not *that* many levels: in fact, I think md.c is the only level
> that would just have to pass it through without doing anything useful.
> I think that working from there is a saner and more efficient approach
> than what you're sketching.
>
> If you want a concrete design sketch, consider this:

Okay, here's a patch implementing this idea.  It seems to work quite
well, and it solves the problem in a limited testing scenario -- I
haven't yet tested on the customer machines.

This customer is running on 8.4 so I started from there; should I
backpatch this to 8.2, or not at all?  (I have all the branches ready
anyway.)

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment

pgsql-hackers by date:

Previous
From: Joshua Berkus
Date:
Subject: Re: reducing the overhead of frequent table locks - now, with WIP patch
Next
From: "Joshua D. Drake"
Date:
Subject: Re: reducing the overhead of frequent table locks - now, with WIP patch