On Wed, Nov 19, 2014 at 11:49 PM, David Rowley dgrowle...@gmail.com wrote:
On Sun, Nov 16, 2014 at 12:19 PM, David Rowley dgrowle...@gmail.com
wrote:
On Sun, Nov 16, 2014 at 10:09 AM, Simon Riggs si...@2ndquadrant.com
wrote:
I propose that we keep track of whether there are any
Hi,
PostgreSQL check-world regress failed with current GIT HEAD on my Kubuntu
14.10.
uname -a
Linux vlD-kuci 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:13:18 UTC
2014 i686 athlon i686 GNU/Linux
gdb -d /home/src/postgresql-devel/postgresql-git/postgresql/src -c core
...
Loaded symbols
I wrote:
The core of that complaint is that we'd have to make ASSERT a plpgsql
reserved word, which is true enough as things stand today. However,
why is it that plpgsql statement-introducing keywords need to be
reserved? The only reason for that AFAICS is to allow us to distinguish
the
On 2014-11-21 10:59:23 -0800, Josh Berkus wrote:
On 11/21/2014 10:54 AM, Stephen Frost wrote:
* Josh Berkus (j...@agliodbs.com) wrote:
Either way, from the code it is clear that we only stay in recovery if
standby_mode is directly turned on. This makes the whole check for a
specially
On 2014-11-21 10:12:40 -0500, Stephen Frost wrote:
* Andres Freund (and...@2ndquadrant.com) wrote:
I still think this change makes the error message more verbose, without
any win in clarity.
Can we agree that there should be consistency?
Consistency with what? Are you thinking of the
On 2014-11-21 08:31:01 -0500, Robert Haas wrote:
On Thu, Nov 20, 2014 at 8:31 PM, Andres Freund and...@2ndquadrant.com wrote:
I can't follow that logic. Why do you think self-exclusive locks are
the only ones that matter?
All the others can be acquired by jumping in front of the lock's
On 23 November 2014 14:45, Amit Kapila Wrote
Thanks a lot for debugging and fixing the issue..
The stacktrace of crash is as below:
#0 0x0080108cf3a4 in .strlen () from /lib64/libc.so.6
#1 0x0080108925bc in ._IO_vfprintf () from /lib64/libc.so.6
#2 0x0080108bc1e0 in
On Mon, Nov 24, 2014 at 7:34 AM, Dilip kumar dilip.ku...@huawei.com wrote:
On 23 November 2014 14:45, Amit Kapila Wrote
Thanks a lot for debugging and fixing the issue..
Latest patch is attached, please have a look.
I think still some of the comments given upthread are not handled:
a.
On Sun, Nov 23, 2014 at 2:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Etsuro Fujita fujita.ets...@lab.ntt.co.jp writes:
(2014/11/19 18:21), Ashutosh Bapat wrote:
Ok. I added that comment to the commitfest and changed the status to
ready for commiter.
Many thanks!
I committed this with
Hearing nothing from the original author, this patch that was in state
Waiting on Author for a couple of days is switched to returned with
feedback.
Regards,
--
Michael
10 matches
Mail list logo