Postgre and AIO
| От | Weck, Luis |
|---|---|
| Тема | Postgre and AIO |
| Дата | |
| Msg-id | IA3PR10MB8113DB0A2CA1B6B0DE3831078D1BA@IA3PR10MB8113.namprd10.prod.outlook.com обсуждение исходный текст |
| Ответы |
Re: Postgre and AIO
Re: Postgre and AIO |
| Список | pgsql-general |
This is more of a question of capability and to make me understand how exactly AIO work in Postgres.
Now that AIO landed in v18, I was thinking of a use case which has annoyed me sometimes, which is inserting lots of data into a table with many indices. What I am specifically “complaining” is that index updating happens one at a time. Would it be possible/make sense to use AIO to do this?
Another thing that happens often is that an index lookup for something like SELECT y FROM tbl WHERE x IN (1,2,…N) where N is a big number such as 1000 or 2000, takes a while, because (at least for versions < 18) it took a long time sequentially reading the index for each value. I ended up having to split the values into smaller chunks and ran multiple queries in parallel to maintain a lower latency overall.
Anyway, does any of this make sense? Could Postgres extend the use of AIO to such cases?
В списке pgsql-general по дате отправления: