From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Tyler <stephen(at)stephen-tyler(dot)com> |
Cc: | Jan Otto <asche(at)me(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: drop tablespace error: invalid argument |
Date: | 2009-11-10 19:03:50 |
Message-ID: | 3458.1257879830@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Tyler <stephen(at)stephen-tyler(dot)com> writes:
> On Tue, Nov 10, 2009 at 8:57 PM, Jan Otto <asche(at)me(dot)com> wrote:
>>> Someone else please confirm? If so I'll revert that patch.
>>
>> Yes i can confirm that this bug is fixed in Mac OS X 10.6.2. I have checked
>> it twice.
>> With removed workaround in tablespace.c and with my self written testcase
>> from
>> september.
> I can confirm that I am no longer able to trigger "ERROR: could not read
> directory "pg_xlog": Invalid argument" in Mac OS X 10.6.2 with
> "checkpoint_segments = 128".
OK, I've reverted the hack in tablespace.c. This is good, I was not
looking forward to providing our own implementation of readdir() :-(
> PS: I am observing some kind of disk lock-up on my machine that I can't
> explain (and is present on both 10.6.1 and 10.6.2). Huge operations (like
> "VACUUM FULL on a 50GB table") appear to run in brief spikes of activity
> interspersed with 30 second pauses when the disk appears to be both inactive
> and somewhat unresponsive and CPU is idle. Perhaps fsync() is misbehaving
> (I have an SSD Raid 0 array).
Maybe ktrace and/or dtrace would shed a bit of light on what's happening
there.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-11-10 19:04:35 | Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled |
Previous Message | Alvaro Herrera | 2009-11-10 18:59:19 | Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled |