Re: Postmaster holding unlinked files for pg_largeobject table
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Kevin Grittner <kevin.grittner@wicourts.gov>, alexk <alexk@commandprompt.com>, Alexander Shulgin <ash@commandprompt.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-09T18:45:31Z
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> writes: > Excerpts from Tom Lane's message of mi jun 08 14:28:02 -0400 2011: >> Alvaro Herrera <alvherre@commandprompt.com> writes: >>> This customer is running on 8.4 so I started from there; should I >>> backpatch this to 8.2, or not at all? >> I'm not excited about back-patching it... > Bummer. Well, of course mine is only one opinion; anybody else feel this *is* worth risking a back-patch for? My thought is that it needs some beta testing. Perhaps it'd be sane to push it into beta2 now, and then back-patch sometime after 9.1 final, if no problems pop up. regards, tom lane