Re: Qualifying use of separate TABLESPACES (performance/functionality)

2024-07-17 Thread Imndlf8r
On 7/16/2024 9:57 PM, Christophe Pettus wrote: On Jul 16, 2024, at 21:45, imndl...@gmx.com wrote: Or, does Postgres expect to be able to access any media however it wants (i.e., R/w), regardless of the expected access patterns of the data stored there? Well, yes and no. PostgreSQL will not res

Qualifying use of separate TABLESPACES (performance/functionality)

2024-07-16 Thread Imndlf8r
Hi, I'm designing an appliance (think: 24/7/365/decades) in which Postgres will act as a "skin" on the sole persistent store. I.e., there is no "filesystem" visible to clients; *all* persistent (and temporary/shared) data is presented through Postgres. There are three different types of data ma