From: | "Ivan Zolotukhin" <ivan(dot)zolotukhin(at)gmail(dot)com> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_start_backup() takes too long |
Date: | 2008-09-29 09:39:58 |
Message-ID: | 751e56400809290239o4ed25292o13d023bd14753b0d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Guys,
This is all not about checkpoints. As I've mentioned in the first
message, even right after manual run of CHECKPOINT command in psql
pg_start_backup() takes same time (~10 minutes).
Regards,
Ivan
On Sun, Sep 28, 2008 at 8:18 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> On Sun, 2008-09-28 at 08:35 -0700, Joshua D. Drake wrote:
>> Ivan Zolotukhin wrote:
>> > Hello,
>> >
>> > Nothing bad both in system and postgres logs :( No serious activity
>> > during backup. I've had to change statement_timeout for backup user to
>> > make it work. But I cannot reproduce this case unfortunately.
>>
>> This is actually not uncommon and PostgreSQL shows exactly nothing in
>> terms of why it is taking so long. The only assumption I have come up
>> with is that start_backup does cause a checkpoint.
>
> Yes, it does a normal checkpoint and writes a file. No reason for it to
> take longer than any other checkpoint.
>
> At 8.2 and below checkpoints were frequently delayed on busy systems.
> This was because of lwlock starvation during commit phase of
> transactions. That was fixed in 8.3.
>
> --
> Simon Riggs www.2ndQuadrant.com
> PostgreSQL Training, Services and Support
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Allison | 2008-09-29 09:49:36 | Re: NULL values seem to short-circuit my unique index |
Previous Message | Oleg Bartunov | 2008-09-29 07:51:52 | Re: [GENERAL] PostgreSQL Cache |