WAL replay of TRUNCATE can take a very long time when shared_buffers is huge. #PostgreSQL
-
-
-
Replying to @pg_xocolatl
as far as i can remember, it needs to scan whole shared_buffers to pick up the buffers which contain the table data to truncate.
1 reply 0 retweets 0 likes -
Replying to @fujii_masao
That's what I thought. DROP TABLE needs to do that too.
1 reply 0 retweets 0 likes -
-
Replying to @fujii_masao @pg_xocolatl
I think that is one reason why
@AndresFreundTec has suggested that we could consider a tree data structure (probably radix trees) to index buffer pool pages. Then you could do a range scan for buffer tags with OID = 42 instead of a full scan.2 replies 0 retweets 4 likes
I even have a prototype patch ;)
11:35 AM - 8 Mar 2018
0 replies
2 retweets
7 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.