On Mon, Aug 10, 2020 at 1:45 PM Israel Brewster
wrote:
>
>
> > On Aug 10, 2020, at 12:06 PM, Peter J. Holzer wrote:
> >
> > On 2020-08-10 09:10:00 -0800, Israel Brewster wrote:
> >> I would point out, however, that using a V1 UUID rather than a V4 can
> >> help with this as it is sequential, not
On 8/10/20 10:53 AM, Stephen Frost wrote:
Greeitngs,
* Ron (ronljohnso...@gmail.com) 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?
> On Aug 10, 2020, at 12:06 PM, Peter J. Holzer wrote:
>
> On 2020-08-10 09:10:00 -0800, Israel Brewster wrote:
>> I would point out, however, that using a V1 UUID rather than a V4 can
>> help with this as it is sequential, not random (based on MAC address
>> and timestamp + random).
>
> If I
On 2020-08-10 09:10:00 -0800, Israel Brewster wrote:
> I would point out, however, that using a V1 UUID rather than a V4 can
> help with this as it is sequential, not random (based on MAC address
> and timestamp + random).
If I read the specs correctly, a V1 UUID will roll over every 429
seconds.
> I would point out, however, that using a V1 UUID rather than a V4 can
help with this as it is sequential, not random (based on MAC address and
timestamp + random)
I wanted to make this point, using sequential UUIDs helped me reduce write
amplification quite a bit with my application, I didn't u
Greetings,
* Israel Brewster (ijbrews...@alaska.edu) wrote:
> > On Aug 10, 2020, at 8:53 AM, Stephen Frost wrote:
> > * Ron (ronljohnso...@gmail.com) 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
---
Israel Brewster
Software Engineer
Alaska Volcano Observatory
Geophysical Institute - UAF
2156 Koyukuk Drive
Fairbanks AK 99775-7320
Work: 907-474-5172
cell: 907-328-9145
> On Aug 10, 2020, at 8:53 AM, Stephen Frost wrote:
>
> Greeitngs,
>
> * Ron (ronljohnso...@gmail.com) wrote:
>> On
On 8/10/20 9:51 AM, Ron wrote:
On 8/10/20 11:38 AM, Ravi Krishna wrote:
[snip]
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?
You mean 32 digits for 128 bits?:
https://www.postgresq
Greeitngs,
* Ron (ronljohnso...@gmail.com) 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
On 8/10/20 11:38 AM, Ravi Krishna wrote:
[snip]
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?
--
Angular momentum makes the world go 'round.
UUID are also random and not correlated with time typically, so with a very
large table when accessing primarily recent data, hitting an index on a big
table will pull random pages into memory instead of primarily the end of
the index.
Both can handle concurrent writes. auto-increment is nothing but serial or
sequence cols and they can handle unique concurrent request. That is why
sometimes you may have gaps.UUID is not only unique, but is also unique across
space. You can have two different databases generate UUID at the sa
Hi,
for web application is it needed to use UUID or auto-increment?
1- if two user inserts row at the same time, does it work?
2- dose the database give the same id for both users or execute one of them
first? ( I mean ID conflict not happens?)
Thanks.
13 matches
Mail list logo
