Re:How Figma's databases team lived to tell the scale
by jamesfinlayson on Thursday March 14, 2024 @06:15PM
(#39709583)
I remember Postgres table spaces being used to separate customers at a previous job - I can't remember how migrations were handled (pretty sure they were applied per table space) but I don't think it was a problem (at our scale anyway).
Re:How Figma's databases team lived to tell the scale
by vmfunction on Thursday March 14, 2024 @07:19PM
(#39710156)
>There is usually not much point in making more than one tablespace per logical file system, since you cannot control the location of individual files within a logical file system. However, PostgreSQL does not enforce any such limitation, and indeed it is not directly aware of the file system boundaries on your system. It just stores files in the directories you tell it to use.
seems like the limitation is the logical file system. Which probably will work for most users.
Re:How Figma's databases team lived to tell the scale
by yard2010 on Thursday March 14, 2024 @06:27PM
(#39709679)
I worked in a place that had a database for each tenant and the schema migrations were a real pain. Every time everything goes smoothly except these few databases that have an edge case that screws the whole migration.
In practice there isn't a big difference, they just colocate several customers according to their sharding key in the same logical database.