Re:Updating a 50 terabyte PostgreSQL database (2018)
by hardwaresofton on Tuesday March 23, 2021 @09:15AM
(#26554580)
Ah thanks -- I was wondering why they wouldn't mention it if it was ZFS, would have made a good addition to the article. I guess they didn't say because it was something proprietary?
[ Parent
| on HN ]
Re:Updating a 50 terabyte PostgreSQL database (2018)
by znpy on Tuesday March 23, 2021 @08:33PM
(#26562110)
No idea, I actually came to the comments for the same reason: looking for details about the storage.
In my opinion it's either zfs or netapp. Zfs can replicate datasets via zfs send, netapp has a snapmirror functionality that does basically the same.
Also, iirc, netapp is contributor to freebsd, so it might be zfs anyway underneath.
I wouldn't be surprised. Last time I had the pleasure to create a snapshot for a volume in a netapp it kinda felt like creating a zfs snapshot, in term of speed and ease.
I thought of netapp since they're running fancy 768gb boxes. If they spend money well on their hardware, they probably spend money well on their storage too.
Re:Updating a 50 terabyte PostgreSQL database (2018)
by hardwaresofton on Wednesday March 24, 2021 @06:24AM
(#26565427)
Yeah zfs send (and a bunch of other features/architecture choices) have been one of the biggest reasons I'm interested in the zfs ecosystem and kind of keep a lookout for it/finding ways to work it into infrastructure that I build. I know that Hardware RAID is what the big boys use, but assuming the performance hit is OK, the feature set of ZFS with a properly tuned database installation like a match made in heaven, was hoping to have them comment...