On Tue, Feb 16, 2010 at 7:20 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> 2010/2/16 Fujii Masao <masao(dot)fujii(at)gmail(dot)com>:
>> On Tue, Feb 16, 2010 at 12:37 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> With the libpq fixes, I get further (more on that fix later, btw), but
>>> now I get stuck in this. When I do something on the master that
>>> generates WAL, such as insert a record, and then try to query this on
>>> the slave, the walreceiver process crashes with:
>>> PANIC: XX000: could not write to log file 0, segment 9 at offset 0, length 160:
>>> Invalid argument
>>> LOCATION: XLogWalRcvWrite, .\src\backend\replication\walreceiver.c:487
>>> I'll keep digging at the details, but if somebody has a good idea here.. ;)
>> Yeah, this problem was reproduced in my (very slow :-( ) MinGW environment, too.
>> Though I've not idenfied the cause yet, I guess that it derives from wrong use
>> of the type of local variables in XLogWalRcvWrite(). I'll continue investigation
>> of it.
> I will be somewhat spottily available over the next two days due to
> on-site work with clients.
> Let me know if you would be helped by some details of how to get a
> (somewhat faster) EC2 image up and running with MSVC to test on :-)
Thanks! I can probably use the EC2 image by reading your great blog post.
But it might take some time to make my sysadmin open the port for
rdesktop for some reasons...
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Hitoshi Harada||Date: 2010-02-16 12:52:12|
|Subject: Re: ToDo: plpgsql plugin for query and expression verification|
|Previous:||From: Kevin Grittner||Date: 2010-02-16 12:31:08|
|Subject: Re: LISTEN/NOTIFY and notification timing guarantees|