Tom Lane wrote:
Simon Riggs <simon@xxxxxxxxxxxxxxx> writes:
On Tue, 2007-12-11 at 22:21 -0500, Tom Lane wrote:
Yeah, restoring is known to be less than speedy, because essentially
zero optimization work has been done on it.
If there was a patch to improve this, would it be applied to 8.3?
Good grief, no. We have not even done the research to find out where
the bottleneck(s) is/are. We're not holding up 8.3 while we go back
into development mode, especially not when this problem has existed
for seven or eight years (even if JD failed to notice before) and
there are already some improvements for it in 8.3.
I would also note that this "problem" is only going to be noticeable on
the highest velocity of databases. This is certainly a 10% of the users
issue. It would be great to get it fixed but there are ways around it
(namely making sure you are running pg_standby and pushing logs at
smaller intervals).
Sincerely,
Joshua D. Drake
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
