| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: AWS vs GCP storage |
| Date: | 2022-02-22 20:50:04 |
| Message-ID: | 3e475129-3beb-f4fb-0040-8120185ca36c@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/22/22 12:27, Torsten Förtsch wrote:
> Hi,
>
> I have a few databases with several TB-sized tables. We recently moved
> one of those databases from AWS EC2 to GCP. Today I ran VACUUM FREEZE on
> those tables and every time I saw our application freezing up (and
> throwing tons of errors) for a few minutes right after the message about
> the end of vacuum (duration: 30182257.392 ms statement: vacuum freeze
> verbose ...). We never saw anything like that on AWS.
And the errors where?
>
> The database is 9.6. At the moment I have no details about the storage
> configuration on GCP. The machine was set up by another department.
>
> Any suggestions on why that is happening and how to prevent it would be
> appreciated.
>
> Thanks,
> Torsten
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Samokhvalov | 2022-02-22 21:38:48 | Re: AWS vs GCP storage |
| Previous Message | Torsten Förtsch | 2022-02-22 20:27:39 | AWS vs GCP storage |