On Wed, 15 Jun 2005, Stefan Kaltenbrunner wrote:
Teodor Sigaev wrote:
btree manages to avoid calling the index support functions during WAL
restore --- can't you do the same? Perhaps you need to be including
more information in the initial xlog records, so that the cleanup step
has everything it needs. Or resort to brute-force search (which is more
or less what btree does). I don't think this operation needs to be very
efficient, since it's a corner case that should only seldom be invoked.
I've just commited WALogging for GiST. It works for online backup
(normal recovery) and mostly after crash, but in this case it can't
restore inclompleted inserts although it can detected and say to log
thet it's needed to reindex GiST index.
FYI: we now have at least 4 machines(otter,kingfisher,lionfish,corgi) on
the buildfarm crashing during testing of GIST-related things in contrib.
Any chance this could be related to this change ?
Most probably :) But, wait a little bit.
We have a patch currently tested and I see no problem with all GiST-based
contribs on my Slackware Linux 10.1 using it.
Stefan
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
