Josh Kupershmidt writes:
> I am pretty sure this is an easily-reproducible crash on git head
> (well, as of a2a480af889b5), helpfully confirmed on IRC by wulczer and
> deko. I reproduced the crash myself on OS X and 64-bit Debian.
> create table foo (a int);
> CREATE RULE notify_foo_updates AS ON
On Thu, May 16, 2013 at 3:33 PM, Josh Kupershmidt wrote:
> Backtrace looks like this:
My mistake -- the last backtrace was from an idle client before the
crash. Thank you andres and wulczer for the correction. Here is the
interesting one:
(gdb) bt
#0 has_unnamed_full_join_using (jtnode=0x0) at
I am pretty sure this is an easily-reproducible crash on git head
(well, as of a2a480af889b5), helpfully confirmed on IRC by wulczer and
deko. I reproduced the crash myself on OS X and 64-bit Debian.
---
create table foo (a int);
CREATE RULE notify_foo_updates AS ON UPDATE TO foo DO NOTIFY foo;
\d
