From: | David Wall <d(dot)wall(at)computer(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Large objects oids |
Date: | 2008-06-10 18:22:58 |
Message-ID: | 484EC682.4080203@computer.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Since large objects use OIDs, does PG 8.3 have a limit of 4 billion
large objects across all of my various tables (actually, I presume OIDs
are used elsewhere besides just large objects)?
Is there any plan on allowing large objects to support more than 2GB?
As data gets larger and larger, I can see this being a problem if you'd
like the ACID properties of a DB to work with video and other large data
sets.
Since all large objects are stored in the pg_catalog.pg_largeobject
table, will running 'vacuum full' on it reduce the FSM issues I often
see with errors like:
WARNING: relation "pg_catalog.pg_largeobject" contains more than
"max_fsm_pages" pages with useful free space
HINT: Consider using VACUUM FULL on this relation or increasing the
configuration parameter "max_fsm_pages".
NOTICE: number of page slots needed (1045968) exceeds max_fsm_pages
(300000)
Thanks,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-06-10 18:26:42 | Re: [ANNOUNCE] PostgreSQL Software Catalogue |
Previous Message | Leif B. Kristensen | 2008-06-10 17:09:27 | Re: REGEXP_REPLACE woes |