Re: How should we design our tables and indexes
| От | Michał Kłeczek |
|---|---|
| Тема | Re: How should we design our tables and indexes |
| Дата | |
| Msg-id | 19C4B423-9982-47C1-B37F-E73EA00E2145@kleczek.org обсуждение исходный текст |
| Ответ на | How should we design our tables and indexes (veem v <veema0000@gmail.com>) |
| Список | pgsql-general |
On 10 Feb 2024, at 20:38, veem v <veema0000@gmail.com> wrote:Hello,
We want to have the response time in <1 sec for our UI search query requirement. These will be pagination queries. These read queries will be on big transaction tables (will have ~500+ attributes approx will have approx. rows size of ~1KB) having a continuous stream of inserts consumed from source. And these tables will be a daily range partitioned on the processing_date column. Each partition is going to hold approx ~450million rows when it will serve in full capacity to all the customers transactions.
You might want to take a look at https://www.postgresql.org/message-id/3FA1E0A9-8393-41F6-88BD-62EEEA1EC21F%40kleczek.org - it works quite well for us and maybe it is something you might want to test yourself.
—
Michal
В списке pgsql-general по дате отправления: