| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Andras Fabian <Fabian(at)atrada(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PG_DUMP very slow because of STDOUT ?? |
| Date: | 2010-07-13 07:45:12 |
| Message-ID: | AANLkTilXfi21NDk_YPNpSx0kmvUcwCrG75CeLE_Na5jX@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jul 13, 2010 at 12:31 AM, Andras Fabian <Fabian(at)atrada(dot)net> wrote:
> Hi Scott,
>
> Although I can't guarantee for 100% that there was no RAID rebuild at some point, I am almost sure that it wasn't the case. Two machines - the ones which were already in production - exhibited this problem. Both of them were already up for some weeks. Now, the reboot rather "fixed" one of them instead of making it worse (as your theory goes this way) the problem "disappeared" (but I don't know for how long). Now, only one of the production machines has the issue ... the one which wasn't rebooted. Strange, strange. Nevertheless thank you for your idea ... this is exactly the way I try to approach the problem, by making some theories and trying to prove or disapprove them :-)
> Now I will try to further investigate along the tips from Craig and Greg.
Was there maybe a kernel update that hadn't been applied by reboot?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andras Fabian | 2010-07-13 07:53:07 | Re: PG_DUMP very slow because of STDOUT ?? |
| Previous Message | Scott Marlowe | 2010-07-13 07:44:08 | Re: "attempted to lock invisible tuple" error while update |