On Fri, Jun 08, 2007 at 11:11:05AM -0400, Tom Lane wrote: > > I wonder if Slony is doing it to you --- somehow deciding it needs to > "replicate" that table from somewhere else. Might be worth inquiring > on the slony lists if anyone's seen such a thing. The only way Slony would do that is in the event that the table were added to a set. In that case, it will indeed truncate the table and try to load the data from the origin. So that is a possibility I didn't list in my other mail. If the table is large, the load could take some time, during which you'd not be able to see anything in the table. When you went to insert to the table, though, you'd get errors, so unless you're dropping the table and rebuilding from scratch, I'd expect you to get an error when you reloaded the data. A -- Andrew Sullivan | ajs@xxxxxxxxxxxxxxx Everything that happens in the world happens at some place. --Jane Jacobs
