Re: Using PK value as a String
От | Merlin Moncure |
---|---|
Тема | Re: Using PK value as a String |
Дата | |
Msg-id | b42b73150808120729x79f893f1m6fc97c6c71a8c44b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Using PK value as a String (Gregory Stark <stark@enterprisedb.com>) |
Список | pgsql-performance |
On Tue, Aug 12, 2008 at 9:46 AM, Gregory Stark <stark@enterprisedb.com> wrote: > "Mark Mielke" <mark@mark.mielke.cc> writes: > >> - Increased keyspace. Even if keyspace allocation is performed, an int4 only >> has 32-bit of keyspace to allocate. The IPv4 address space is already over 85% >> allocated as an example of how this can happen. 128-bits has a LOT more >> keyspace than 32-bits or 64-bits. > > The rest of your points are valid (though not particularly convincing to me > for most applications) but this example is bogus. The IPv4 address space is > congested because of the hierarchic nature of allocations. Not because there > is an actual shortage of IPv4 addresses themselves. There would be enough IPv4 > for every ethernet device on the planet for decades to come if we could > allocate them individually -- but we can't. Only because of NAT. There are a _lot_ of IP devices out there maybe not billions, but maybe so, and 'enough for decades' is quite a stretch. merlin
В списке pgsql-performance по дате отправления: