| From: | Michał Kłeczek <michal(at)kleczek(dot)org> |
|---|---|
| To: | veem v <veema0000(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How should we design our tables and indexes |
| Date: | 2024-02-11 07:29:29 |
| Message-ID: | 19C4B423-9982-47C1-B37F-E73EA00E2145@kleczek.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 10 Feb 2024, at 20:38, veem v <veema0000(at)gmail(dot)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.
>
>
[snip]
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | veem v | 2024-02-11 07:55:10 | Re: How to do faster DML |
| Previous Message | veem v | 2024-02-11 07:23:10 | Re: How should we design our tables and indexes |