On Mon, Mar 2, 2015 at 12:38 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>
> There is an issue if you do a dump and restore: the toast OIDs used in any
> one table will be consecutive after that, because we load all the data for
> each table sequentially.
With these consecutive oids, the "aggravated oid wrap around" can be
illustrated by the following example:
- table A oids in [minOid, 2^31)
- table B oids in [2^31, 2^32]
After 1st time wrap around, and follows an insert(A), it immediately
bumps oid to 2^31. Now it is B's turn, it has to bump it to 2^32 and
wrap it around the 2nd time. This extreme example shows that we can
incur another wrap around with 2 toast insertions.
It is not clear how above example can be translated into real world
scenario probabilistically ("many more interleaved ranges (down) with
many more concurrency (up)"), but the "aggravated" issue seems there.
Regards,
Qingqing
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
