From: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
---|---|
To: | Rondat Flyag <rondatflyag(at)yandex(dot)ru> |
Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Queries containing ORDER BY and LIMIT started to work slowly |
Date: | 2023-08-29 21:06:54 |
Message-ID: | CAMAYy4+Db52kJMa3mVvxUe4wes-UgPL5NCrFMgxviOvKgZeb7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Aug 29, 2023 at 3:57 PM Rondat Flyag <rondatflyag(at)yandex(dot)ru> wrote:
> I took the dump just to store it on another storage (external HDD). I
> didn't do anything with it.
>
> 29.08.2023, 21:42, "Jeff Janes" <jeff(dot)janes(at)gmail(dot)com>:
>
>
>
> On Tue, Aug 29, 2023 at 1:47 PM Rondat Flyag <rondatflyag(at)yandex(dot)ru>
> wrote:
>
> I have a legacy system that uses `Posgresql 9.6` and `Ubuntu 16.04`.
> Everything was fine several days ago even with standard Postgresql
> settings. I dumped a database with the compression option (maximum
> compression level -Z 9) in order to have a smaller size (`pg_dump
> --compress=9 database_name > database_name.sql`). After that I got a lot of
> problems.
>
>
> You describe taking a dump of the database, but don't describe doing
> anything with it. Did you replace your system with one restored from that
> dump? If so, did vacuum and analyze afterwards?
>
> Cheers,
>
> Jeff
>
>
Since this is a very old system and backups are fairly I/O intensive, it is
possible you have a disk going bad? Sometimes after doing a bunch of I/O
on an old disk, it will accelerate its decline. You could be about to lose
it altogether.
From | Date | Subject | |
---|---|---|---|
Next Message | Rondat Flyag | 2023-08-30 17:31:05 | Re: Queries containing ORDER BY and LIMIT started to work slowly |
Previous Message | Jeff Janes | 2023-08-29 20:11:39 | Re: Queries containing ORDER BY and LIMIT started to work slowly |