Foreground vacuum and buffer access strategy - Mailing list pgsql-hackers

From Jeff Janes
Subject Foreground vacuum and buffer access strategy
Date
Msg-id CAMkU=1yV=Zq8sHviv5Nwajv5woWOvZb7bx45rgDvtxs4P6W1Pw@mail.gmail.com
Whole thread Raw
Responses Re: Foreground vacuum and buffer access strategy
List pgsql-hackers
If I invoke vacuum manually and do so with VacuumCostDelay == 0, I
have basically declared my intentions to get this pain over with as
fast as possible even if it might interfere with other processes.

Under that condition, shouldn't it use BAS_BULKWRITE rather than
BAS_VACUUM?  The smaller ring size leads to a lot of synchronous WAL
flushes which I think can slow the vacuum down a lot.

Cheers,

Jeff


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Archiver not exiting upon crash
Next
From: Heikki Linnakangas
Date:
Subject: Re: Bug in new buffering GiST build code