Re: Postmaster holding unlinked files for pg_largeobject table

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Alvaro Herrera" <alvherre@commandprompt.com>, "Tom Lane" <tgl@sss.pgh.pa.us>

Cc: "alexk" <alexk@commandprompt.com>, "Alexander Shulgin" <ash@commandprompt.com>, "pgsql-hackers" <pgsql-hackers@postgresql.org>

Date: 2011-06-06T16:23:52Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Reset reindex-in-progress state before reverifying an exclusion constraint.
- dccfb72892ac 9.1.0 cited

Alvaro Herrera <alvherre@commandprompt.com> wrote:
 
> That doesn't solve the WAL problem Kevin found, of course ...
 
I wouldn't worry about that too much -- the WAL issue is
self-limiting and not likely to ever cause a failure.  The biggest
risk is that every now and then some new individual will notice it
and waste a bit of time investigating.  The LO issue, on the other
hand, could easily eat enough disk to cause a failure.
 
-Kevin