Search Postgresql Archives

Re: UUID or auto-increment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 8/10/20 10:53 AM, Stephen Frost wrote:
Greeitngs,

* Ron (ronljohnsonjr@xxxxxxxxx) wrote:
On 8/10/20 11:38 AM, Ravi Krishna wrote:
Finally UUID results in write amplication in wal logs.  Keep that in mind
if your app does lot of writes.

Because UUID is 32 bytes, while SERIAL is 4 bytes?

and because it's random and so will touch a lot more pages when you're
using it...

Avoid UUIDs if you can- map them to something more sensible internally
if you have to deal with them.

Thanks,

Stephen

I suspect the increased storage cost is more related to the size of the record than to the ratio of the data types.

What says two consecutively saved records ought to be stored on the same page or will likely be sought with the same search criterion. Serial ids put a time order (loosely) on the data which may be completely artificial.





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux