Lenny,

We had a library version incompatibility on one of the mapservers that caused 
all the requests it attempted to handle to fail.  We rebuilt and reinstalled 
the (seemingly) messed up one and it appears to be working properly now.  Could 
you see if the error rate has dropped to (near) zero?

Thanks in advance and thanks for the vigilance…

Karl

On Sep 26, 2010, at 2:00 PM, 
<[email protected]<mailto:[email protected]>>
 wrote:

Send Slony1-general mailing list submissions to
[email protected]<mailto:[email protected]>

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.slony.info/mailman/listinfo/slony1-general
or, via email, send a message with subject or body 'help' to
[email protected]

You can reach the person managing the list at
[email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Slony1-general digest..."
Today's Topics:

  1. Re: ERROR: cache lookup failed for type 14237017
     (Aleksey Tsalolikhin)

From: Aleksey Tsalolikhin <[email protected]>
Date: September 26, 2010 1:22:29 AM CDT
To: <[email protected]>
Subject: Re: [Slony1-general] ERROR: cache lookup failed for type 14237017


On Fri, Sep 24, 2010 at 4:21 PM, Steve Singer <[email protected]> wrote:
On 10-09-24 06:06 PM, Aleksey Tsalolikhin wrote:

 I read the FAQ and will make sure to stop our application next time we drop 
the Slony cluster.

I might suggest briefly mentioning in the Best Practices section of
the documentation
a reference to this issue.

Do you think it be better to mention that in best practices or the section
on uninstalling/removing slony?

Both.  :)    This is really the sort of thing one does not want to
miss / find out the hard way.

Truly,
Aleksey



_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general

_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general

Reply via email to