"Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx> writes: > You're not alone. At first I was assuming that it was because of > archiving, but the OP says that's turned off. Unless it had been on > and there wasn't a *restart* after changing the configuration, Yeah, I was less than convinced by his eyeball report of that, too. "show archive_mode" would be a much more convincing check of the server's state. Or would have been, if the server hadn't been restarted since the problem occurred. archive_mode on with a bad archive_command would lead directly to the reported problem ... although it should also lead to pretty obvious complaints in the postmaster log. (Hmm ... but those complaints are logged at level WARNING, which as discussed elsewhere is really lower than LOG. Should we change them?) regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
