On Thu, Aug 18, 2011 at 4:26 AM, Lonni J Friedman wrote:
> I wish I knew. All the documentation out there always focuses on
> setting up a restore command, as if there would be a huge disaster if
> it wasn't done. Is it safe to simply make wal_keep_segments really
> large, and skip the restore_c
On Mon, Aug 15, 2011 at 9:34 PM, Fujii Masao wrote:
> On Thu, Aug 11, 2011 at 7:19 AM, Lonni J Friedman wrote:
>> First the problem. On *only* one of the two standby servers, I'm
>> seeing errors like the following whenever I issue any SQL commands on
>> the master which write (insert, update, e
On Thu, Aug 11, 2011 at 7:19 AM, Lonni J Friedman wrote:
> First the problem. On *only* one of the two standby servers, I'm
> seeing errors like the following whenever I issue any SQL commands on
> the master which write (insert, update, etc) to the database:
> LOG: invalid record length at 8/7A
Hi.
I've experienced very similar behavior and log message. I do not know what
is the problem in detail but my guess is that standby system has data which
is incompatible to accept streaming replication of the master.
The way I solved is the following on Ubuntu11.04. Suppose postgresql.conf
and r
On Thu, Aug 11, 2011 at 8:17 AM, Pedro Sam wrote:
> Do your machines have the same architecture? (64 bit vs 32 bit)
Yes, they're all Fedora15-x86_64.
--
~
L. Friedman netll...@gmail.com
Llam
Do your machines have the same architecture? (64 bit vs 32 bit)
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or
Greetings,
I've got three Linux systems (each with Fedora15-x86_64 running
PostgreSQL-9.0.4). I'm attempting to get a basic streaming
replication setup going with one master & two standby servers. At
this point, the replication portion appears to be working. I can run
an 'update' statement on th
