Andrew Edson wrote: > I'm having trouble with the dev systems I've been working on. I've > been waiting for a few hours for the database replication to complete > a transaction, which it still hasn't done; a similar transaction > earlier today took about half an hour to finish. The systems in > question are running SuSE 9.3, Postgres 8.1.3, and Slony 1.1.5. > > I took a look at the ps ax output, and I noticed something next to the > postgres entries: All of them except the last are listed as 'idle', > while the last one is listed as 'idle in transaction'. Exactly what > does it mean for a running program to be idle? Is there likely to be > some kind of deadlock condition that's preventing the replication from > finishing? Or is there something else I should be doing to get the > system to work? "<IDLE> in transaction" indicates that there is a transaction open, but that no work is being done at present.
"<IDLE>" indicates that there is a connection, but that it doesn't even have a transaction open. Presumably the connection that's <IDLE> in transaction has some sort of work in progress; don't know what. What you might do is to check what the state of things are on the *other* server involved; I would expect that you'd find that there is some transaction that is quite busy doing some sort of work on the other server, perhaps preparing the queries that pull what data is to get replicated to the subscriber. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
