Fri Jul 25 14:54:49 PDT 2008
- Previous message: [Slony1-general] CREATE SET hung waiting
- Next message: [Slony1-general] Re: [Slony1-hackers] CREATE SET hung waiting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Gurjeet Singh" <singh.gurjeet at gmail.com> writes: > Hi All, > The docs for CREATE SET say 'No application-visible locking should take place'. But we saw that it was hung, and noticed that there was a > VACUUM running on master node. We waited for quite a while, and after we killed that VACUUM, the CREATE SET moved forward. > PG is 8.1.11, and Slony is 1.2.14, if that helps. The only thing that CREATE SET does, initially, that involves locking of *anything* is that it takes out a lock out on sl_config_lock, a table internal to Slony-I. The only way for that to lock things that are application-visible is if you have some application that's vacuuming *everything*, and which therefore takes out a lock on sl_config_lock that prevents it from being granted to the CREATE SET request. The locking that is done should indeed not be visible to applications. It only became visible because you had a VACUUM that was working on the Slony-I schema. I'm trying to think of what more to say, in the documentation; nothing is really coming to me. I don't think that the documentation is misleading. -- select 'cbbrowne' || '@' || 'linuxfinances.info'; http://cbbrowne.com/info/lsf.html Rules of the Evil Overlord #145. "My dungeon cell decor will not feature exposed pipes. While they add to the gloomy atmosphere, they are good conductors of vibrations and a lot of prisoners know Morse code." <http://www.eviloverlord.com/>
- Previous message: [Slony1-general] CREATE SET hung waiting
- Next message: [Slony1-general] Re: [Slony1-hackers] CREATE SET hung waiting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list