On Thu, May 30, 2013 at 12:49 AM, Stephen Scheck
wrote:
> If this hypothesis is correct, doing a vacuum should free up dead pages and
> your size expectations should be more accurate. And if that's the case
> putting more intelligence into the application could mitigate some of the
> update growt
This is just a guess (I haven't dug into the low-level page/disk access
Postgres code for Large Objects yet but if I'm right, the LO-based project
I'm working on will likely face the same issues you're seeing), but LOs
enjoy transactional behavior just like anything else (as far as I can tell
from
