| From: | Virendra Kumar <viru_7683(at)yahoo(dot)com> |
|---|---|
| To: | Pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Copy Statistics Tables During Upgrade |
| Date: | 2021-03-31 18:15:23 |
| Message-ID: | 1042003030.2667942.1617214523822@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello Team,
I was doing an upgrade of one of our PG (9.6.11 to 11.9) database and came across the question that what is reason PostgreSQL is not doing copy of stats and we have to analyze right after upgrade. There are two situations where this will help when we use this DB as our enterprise database:
1. If DB is in magnitude of hundreds of TB and we have to do analyze it might take several hours before we handover this to application services.
2. We are loosing critical information like most common values and most common freqs because these values are populated over time when many-many sessions hit table and queries with different values of a column.
Any input on this is higly appreciated.
Regards,
Virendra Kumar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-31 18:24:10 | Re: Debugging leaking memory in Postgresql 13.2/Postgis 3.1 |
| Previous Message | Stephan Knauss | 2021-03-31 18:08:23 | Re: Debugging leaking memory in Postgresql 13.2/Postgis 3.1 |