Timeline for Postgres Materialized View Dramatically Increasing In Size
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2018 at 1:19 | vote | accept | FluxDipole | ||
| Apr 1, 2018 at 1:19 | answer | added | FluxDipole | timeline score: 12 | |
| Mar 22, 2018 at 18:52 | comment | added | jjanes | Surely you have a test environment, right? Run the non-concurrent refresh against that and see if it shrinks the size. | |
| Mar 22, 2018 at 18:48 | answer | added | Richard Huxton | timeline score: 1 | |
| Mar 22, 2018 at 15:08 | comment | added | FluxDipole | Each row is three bigints. There are two million rows. I can’t run a vacuum full without taking the production site down. | |
| Mar 22, 2018 at 8:13 | comment | added | user1822 | Does the size reduce when you do a vacuum full on the mview? What is your exact Postgres version? | |
| Mar 22, 2018 at 8:00 | comment | added | Imanol Y. | How many rows / size does each materialized view has? | |
| S Mar 22, 2018 at 7:56 | history | suggested | Husam Mohamed | added tags | |
| Mar 22, 2018 at 6:12 | review | Suggested edits | |||
| S Mar 22, 2018 at 7:56 | |||||
| Mar 22, 2018 at 5:15 | review | First posts | |||
| Mar 22, 2018 at 5:37 | |||||
| Mar 22, 2018 at 5:12 | history | asked | FluxDipole | CC BY-SA 3.0 |