On Sat, Mar 29, 2014 at 6:17 PM, Adrian Klaver adrian.kla...@aklaver.comwrote:
On 03/29/2014 08:19 AM, Willy-Bas Loos wrote:
The error that shows up is a Bus error.
That's on the replication slave.
Here's the log about it:
2014-03-29 12:41:33 CET db: ip: us: FATAL: could not receive data
On 03/31/2014 04:12 AM, Willy-Bas Loos wrote:
On Sat, Mar 29, 2014 at 6:17 PM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
On 03/29/2014 08:19 AM, Willy-Bas Loos wrote:
The error that shows up is a Bus error.
That's on the replication
On 03/31/2014 04:12 AM, Willy-Bas Loos wrote:
On Sat, Mar 29, 2014 at 6:17 PM, Adrian Klaver
adrian.kla...@aklaver.com mailto:adrian.kla...@aklaver.com wrote:
And it makes me wonder what else may be issues that arise from that. But
especially, what i can do about it.
Had to go through it
Adrian Klaver adrian.kla...@aklaver.com writes:
On 03/31/2014 04:12 AM, Willy-Bas Loos wrote:
I'm still worried that it's like Tom Lane said in another discussion:So
basically, you've got a broken kernel here: it claimed to give PG circa
(135MB) of memory, but what's actually there is only
On 03/31/2014 08:01 AM, Tom Lane wrote:
Adrian Klaver adrian.kla...@aklaver.com writes:
On 03/31/2014 04:12 AM, Willy-Bas Loos wrote:
I'm still worried that it's like Tom Lane said in another discussion:So
basically, you've got a broken kernel here: it claimed to give PG circa
(135MB) of
Adrian Klaver adrian.kla...@aklaver.com writes:
At this point the memory allocation as a problem is as much conjecture
as anything else, at least to me. So what is causing SIGBUS is an open
question in my mind.
Agreed, it's unproven what's causing the SIGBUS in the case at hand.
However, in
On 03/31/2014 08:28 AM, Tom Lane wrote:
Adrian Klaver adrian.kla...@aklaver.com writes:
At this point the memory allocation as a problem is as much conjecture
as anything else, at least to me. So what is causing SIGBUS is an open
question in my mind.
Agreed, it's unproven what's causing the
The error that shows up is a Bus error.
That's on the replication slave.
Here's the log about it:
2014-03-29 12:41:33 CET db: ip: us: FATAL: could not receive data from WAL
stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
On 03/29/2014 08:19 AM, Willy-Bas Loos wrote:
The error that shows up is a Bus error.
That's on the replication slave.
Here's the log about it:
2014-03-29 12:41:33 CET db: ip: us: FATAL: could not receive data from
WAL stream: server closed the connection unexpectedly
This probably
Hi,
I have a problem with postgres in combination with openvz.
My hot standby crashes on me when i give it a normal value for
shared_buffers (4GB, which 25% of the memory in the container).
When i tune down the shared_buffers, it works again. But of course this is
far from desireable.
Now, i've
On 03/28/2014 01:51 AM, Willy-Bas Loos wrote:
Hi,
I have a problem with postgres in combination with openvz.
My hot standby crashes on me when i give it a normal value for
shared_buffers (4GB, which 25% of the memory in the container).
When i tune down the shared_buffers, it works again. But of
11 matches
Mail list logo
