Sorry for the delay.
On Tue, Apr 3, 2012 at 1:44 AM, masterchief wrote:
> I see. Is there a more elegant way that I could shut down my standby server
> so that it would be in a more clean state? For example, when I first built
> the standby and began replication, I didn't get either of those re
I see. Is there a more elegant way that I could shut down my standby server
so that it would be in a more clean state? For example, when I first built
the standby and began replication, I didn't get either of those record
length messages.
--
View this message in context:
http://postgresql.10456
On Sat, Mar 31, 2012 at 1:20 AM, Eric Simon wrote:
> 2012-03-16 10:27:34 CDT LOG: invalid record length at 9/B9F85E78
> 2012-03-16 10:27:34 CDT LOG: streaming replication successfully connected
> to primary
Just after startup, the standby tries to read and replay the WAL files which
exist in th
Hi,
I'm on 9.1.2 and occasionally get what are probably harmless warning messages
in my logs, but because I have the responsibility of
ensuring we haven't lost a bit of data between our master and standby, I feel I
should know exactly what they mean. I occasionally
see "invalid record length" an
Hi,
I'm on 9.1.2 and occasionally get what are probably harmless warning
messages in my logs, but because I have the responbility of ensuring we
haven't lost a bit of data between our master and standby, I feel I should
know exactly what they mean. I occasionally see "invalid record length" and
