Timeline for Postgres Vacuum in Function
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2022 at 6:00 | history | tweeted | twitter.com/StackDBAs/status/1493102724530978820 | ||
| Jan 7, 2020 at 22:25 | history | edited | CommunityBot |
added [postgresql-performance] to 571 questions - Shog9 (Id=1924)
|
|
| Aug 1, 2017 at 6:47 | vote | accept | Bruno Zamengo | ||
| Jul 31, 2017 at 14:44 | answer | added | Avarkx | timeline score: 5 | |
| Jul 31, 2017 at 14:43 | comment | added | Bruno Zamengo |
Well, the function is run, more or less, twice a week. I think I can go for a VACUUM FULL exclusive lock. Yes, there's a large number of dead rows (last time 50% ~ 4GB). I've tried to manually run cluster (from the client PgAdmin III) but I get the error ERROR: there is no previously clustered index for table "my_table"
|
|
| Jul 31, 2017 at 14:13 | comment | added | Avarkx |
How often is the function run? Are you able to go for a VACUUM FULL, exclusively locking the table for the duration? If there's a large number of dead rows, can you instead use CLUSTER?
|
|
| Jul 31, 2017 at 13:18 | review | First posts | |||
| Jul 31, 2017 at 13:51 | |||||
| Jul 31, 2017 at 13:18 | history | asked | Bruno Zamengo | CC BY-SA 3.0 |