I'm pruning an 8.4 database that was using a *lot* of space in pg_largeobject
(400GB according to my size query). What I've done seems to work, but I don't
know if there's a time-bomb waiting for me, so I have to ask you who've
implemented this part. Steps:
1) On new.better.server.com:
Tom.
./scc
On 2012-10-10, at 11:04 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Scott Corscadden sc...@corscadden.ca writes:
** MY QUESTION ** - Will pg_largeobject automatically choose new OIDs that
don't conflict, if I've added lo's this way, by direct COPY?
In 8.4, yes. In later versions
While I'm referring to the 8.4 release, it's a slightly more general question.
We're moving away from using pg_largeobject as fast as we can, and while doing
so I'm seeing interesting behaviour. I'd like to confirm that this is is
expected, or perhaps I don't have tuning parameters set quite
