| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Jan Gunnar Dyrset <jan(dot)g(dot)dyrset(at)cybernetica(dot)no>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL disk fragmentation causes performance problems on Windows |
| Date: | 2015-04-29 14:56:12 |
| Message-ID: | 5540F10C.9030400@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 04/29/2015 10:35 AM, ktm(at)rice(dot)edu wrote:
> On Wed, Apr 29, 2015 at 07:07:04AM -0700, Joshua D. Drake wrote:
>> On 04/29/2015 01:08 AM, Andres Freund wrote:
>>
>>>> Which OS and filesystem is this done on? Because many halfway modern
>>>> systems, like e.g ext4 and xfs, implement this in the background as
>>>> 'delayed allocation'.
>>> Oh, it's in the subject. Stupid me, sorry for that. I'd consider testing
>>> how much better this behaves under a different operating system, as a
>>> shorter term relief.
>> This is a known issue on the Windows platform. It is part of the
>> limitations of that environment. Linux/Solaris/FreeBSD do not suffer
>> from this issue in nearly the same manner.
>>
>> jD
>>
> You might consider a CLUSTER or VACUUM FULL to re-write the table with
> less fragmentation.
>
Or pg_repack if you can't handle the lockup time that these involve.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-04-30 20:57:19 | Re: PATCH: adaptive ndistinct estimator v4 |
| Previous Message | ktm@rice.edu | 2015-04-29 14:35:43 | Re: PostgreSQL disk fragmentation causes performance problems on Windows |