Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Large Objects
- From: Richard Huxton <dev(at)archonet(dot)com>
- To: haukinger(at)gmx(dot)de
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: Large Objects
- Date: Fri, 23 Feb 2007 08:06:25 +0000
- Message-id: <45DEA081(dot)7000803(at)archonet(dot)com>
haukinger(at)gmx(dot)de wrote:
Hi all ! I'm working on a database that needs to handle insertion of about 100000 large objects (50..60GB) a day. It should be able to run 200 days, so it will become about 10TB eventually, mostly of 200..500KB large objects. How does access to large objects work ? I give the oid and get the large object... what is done internally ? How (if at all) are the oid's indexed ?
Albe's answered your actual question, but I'd wonder if you really want to do this?
The key question is whether you need to have the actual objects stored under transactional control. If not, just saving them as files will prove much more efficient.
-- Richard Huxton Archonet Ltd
- References:
- Large Objects
- From: haukinger
- Large Objects
- Prev by Date: Re: Supported plpgsql BEFORE ... EACH ROW behavior
- Next by Date: Re: PGSQL Locking vs. Oracle's MVCC
- Previous by thread: Re: Large Objects
- Next by thread: Complex search advice?
- Indexes: