|
Tom Lane wrote: David Wall <d.wall@xxxxxxxxxxxx> writes: What's a rough estimate of "a lot less"? Are we talking 2 billion, 3 billion, 1 billion? Isn't there just one catalog per postmaster instance (pg_catalog)? The issue we have is that one postmaster runs a large number of databases (let's say 100 for easy calculations), so even with the max 4 billion potential OIDs, that would drop each DB to 40 million each. Part of this is just architectural to us. We do heavy encryption/compression of data (in particular digitally signed XML text) and use large objects to store these, but we may need to change these to use bytea since they wouldn't use up OIDs and the actual data size tends not to be too large (perhaps 10KB compressed and encrypted binary data) and can be done in a block. All that character escaping of binary data, though, makes the JDBC-to-Postmaster interface a tad bit ugly, though.
Too bad, but again, we can always work around it, even if means a layer that bundles large objects sort of like large objects bundle bytea. We prefer not to store it outside the database as the large files can get out of sync from the database (ACID properties) and of course need to be backed up separately from the database backups and WAL copying for replication. David |
