Physical Database Configuration
От | Guy Rouillier |
---|---|
Тема | Physical Database Configuration |
Дата | |
Msg-id | 9593420C5541924EA4C94E5FC164F88803E42B@m-tx-exch01.add0.masergy.com обсуждение исходный текст |
Ответы |
Re: Physical Database Configuration
Re: Physical Database Configuration Re: Physical Database Configuration |
Список | pgsql-general |
(Resurrecting a subject I found searching the archives...) Newbie. We're investigating replacing our Oracle databases with PostgreSQL. Our largest database is currently 25 GB and growing. It contains time sequenced data. Under Oracle, we use a partitioned tablespace for the busiest table, so that we can remove old partitions after an aging period. This one table is the majority of that 25 GB. I saw in the referenced sequence of posts that PostgreSQL will close a file for a table once it reaches 1 GB, and start a new file. So I'm concluding PostgreSQL has the ability to span multiple files for a single table. Is there any way for me to control that, so I can get PostgreSQL to start a new file on the 1st of each month? Or is this planned for tablespaces, which I also saw discussed. Thanks. -- Guy Rouillier
В списке pgsql-general по дате отправления: