4 ms·
Gin indexes aren't "plain" indexes - they're used for things like full text search. Depending on the specific types/opclasses that can mean that a lot of work h
by anarazel 5y ago
Gin indexes aren't "plain" indexes - they're used for things like full text search. Depending on the specific types/opclasses that can mean that a lot of work has to be done for a single inserted/updated row.
- VWWHFSfQ 5y agoThe performance table says 5,000/minute even without the GIN index on the table.
- anarazel 5y agoGood point - it's still 22 other indexes though. And it's Aurora, so who knows :). The table is fairly large, so it's quite possible that a lot of the indexes aren't in memory, making the index maintenance more expensive...
- JoelJacobson 5y agoRelated thread on pgsql-hackers: "use AV worker items infrastructure for GIN pending list's cleanup" https://www.postgresql.org/message-id/flat/20210405063117.GA2478%40ahch-to https://www.postgresql.org/message-id/flat/20210405063117.GA... """ A customer here has 20+ GIN indexes in a big heavily used table and every time one of the indexes reaches gin_pending_list_limit (because of an insert or update) a user feels the impact. So, currently we have a cronjob running periodically and checking pending list sizes to process the index before the limit get fired by an user operation. While the index still is processed and locked the fact that doesn't happen in the user face make the process less notorious and in the mind of users faster. This will provide the same facility, the process will happen "in the background". """