Обсуждение: control over database files
Hi,
I am wanting to be able to have control over what files that ables are stored in. Basically I am looking to have literally tens of thousands of tables all of the same type and to be able to store these as separate files in a filing system.
--
Aaron Gray
Independent Open Source Software Engineer, Computer Language Researcher, Information Theorist, and amateur computer scientist.
On 07/17/2018 02:50 PM, Aaron Gray wrote: > Hi, > > I am wanting to be able to have control over what files that ables are > stored in. Basically I am looking to have literally tens of thousands of > tables all of the same type and to be able to store these as separate > files in a filing system. Because? In sense that is what is being done anyway: https://www.postgresql.org/docs/10/static/storage-file-layout.html > > -- > Aaron Gray > > Independent Open Source Software Engineer, Computer Language Researcher, > Information Theorist, and amateur computer scientist. -- Adrian Klaver adrian.klaver@aklaver.com
On Tuesday, July 17, 2018, Aaron Gray <aaronngray.lists@gmail.com> wrote:
I am wanting to be able to have control over what files that ables are stored in. Basically I am looking to have literally tens of thousands of tables all of the same type and to be able to store these as separate files in a filing system.
At first glance your needs and what PostgreSQL provides are incompatible but you can learn the details in the documentation.
That said, you will likely find that the configuration variables that are provided are sufficient to meet most needs and that actual control over low-level details such as file and directory structure are something best left to existing well written software such as PostgreSQL.
You might find that features such as row-level security and/or partitioning (depending on why you need thousands of identical tables...) can either reduce the need for them or make setting them up considerably easier, respectively. IOW, starting with a higher level use case will produce more useful responses.
David J.