On Sat, Oct 5, 2013 at 7:54 PM, Alvaro Herrera alvhe...@2ndquadrant.comwrote:
MauMau escribió:
From: Alvaro Herrera alvhe...@2ndquadrant.com
Can you please send a fixup patch to what's already committed?
OK, I'll send a patch against HEAD, which will be a few lines. Am I
MauMau escribió:
From: Alvaro Herrera alvhe...@2ndquadrant.com
Can you please send a fixup patch to what's already committed?
OK, I'll send a patch against HEAD, which will be a few lines. Am I
understanding the meaning of fixup patch?
Yep, thanks.
Please use the attached patch.
From: Alvaro Herrera alvhe...@2ndquadrant.com
Can you please send a fixup patch to what's already committed?
OK, I'll send a patch against HEAD, which will be a few lines. Am I
understanding the meaning of fixup patch?
Yep, thanks.
Please use the attached patch. Thanks.
Regards
MauMau
From: Alvaro Herrera alvhe...@2ndquadrant.com
Can you please send a fixup patch to what's already committed?
OK, I'll send a patch against HEAD, which will be a few lines. Am I
understanding the meaning of fixup patch?
Regards
MauMau
--
Sent via pgsql-hackers mailing list
MauMau escribió:
From: Alvaro Herrera alvhe...@2ndquadrant.com
Can you please send a fixup patch to what's already committed?
OK, I'll send a patch against HEAD, which will be a few lines. Am I
understanding the meaning of fixup patch?
Yep, thanks.
--
Álvaro Herrera
MauMau escribió:
AbortStartTime 0 is also necessary to avoid sending SIGKILL
repeatedly. I sent the attached patch during the original
discussion. The below fragment is relevant:
Can you please send a fixup patch to what's already committed?
--
Álvaro Herrera
From: Jeff Janes jeff.ja...@gmail.com
--
I've implemented the Min to Max change and did some more testing. Now I
have a different but related problem (which I also saw before, but less
often than the select() one). The 5 second clock doesn't get
On Wednesday, September 11, 2013, Alvaro Herrera wrote:
Noah Misch escribió:
On Tue, Sep 10, 2013 at 05:18:21PM -0700, Jeff Janes wrote:
I think the problem is here, where there should be a Max rather than a
Min:
commit 82233ce7ea42d6ba519aaec63008aff49da6c7af
Author: Alvaro
On Tue, Sep 10, 2013 at 05:18:21PM -0700, Jeff Janes wrote:
I've been getting some failures after an immediate shutdown or crash,
during severe IO stress, with the message:
LOG: XX000: select() failed in postmaster: Invalid argument
LOCATION: ServerLoop, postmaster.c:1560
It is trying
Noah Misch escribió:
On Tue, Sep 10, 2013 at 05:18:21PM -0700, Jeff Janes wrote:
I think the problem is here, where there should be a Max rather than a Min:
commit 82233ce7ea42d6ba519aaec63008aff49da6c7af
Author: Alvaro Herrera alvhe...@alvh.no-ip.org
Date: Fri Jun 28 17:20:53 2013
I've been getting some failures after an immediate shutdown or crash,
during severe IO stress, with the message:
LOG: XX000: select() failed in postmaster: Invalid argument
LOCATION: ServerLoop, postmaster.c:1560
It is trying to sleep for -1 seconds.
I think the problem is here, where there
11 matches
Mail list logo