Wed Sep 22 07:35:43 PDT 2010
- Previous message: [Slony1-general] ERROR: cache lookup failed for type 14237017
- Next message: [Slony1-general] ERROR: cache lookup failed for type 14237017
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aleksey Tsalolikhin <atsaloli.tech at gmail.com> writes: > On Tue, Sep 21, 2010 at 2:04 PM, Aleksey Tsalolikhin > <atsaloli.tech at gmail.com> wrote: >> Dear Steve, >> >> You are right, I saw these errors on the Slony master. The master >> was NOT quiesced for the Slony drop/recreate; data was rolling in. >> >> So does this mean 12,000 queries failed? I don't see anything in >> the database log like "query cancelled" or anything like that. > > I just found in my application logs that I had 35 queries fail earlier in the > Slony cluster drop/recreate timeline than the 12000 ERROR's in the > database log. > > I guess that means I have to put my application into "maintenance mode" > and quisce it before doing a Slony drop/recreate. Is that what people > do, commonly? > > I don't see this on the "Best Practices" page at > http://www.slony.info/documentation/slonyadmin.html, should it be added? It isn't there, but it is in the FAQ... <http://slony.info/documentation/faq.html#AEN7333> -- let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;; Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-general] ERROR: cache lookup failed for type 14237017
- Next message: [Slony1-general] ERROR: cache lookup failed for type 14237017
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list