Re: [HACKERS] trouble with rules

Vadim wrote:

>
> Jan Wieck wrote:
> >
> > >
> > > Hi!
> > >
> > > can somebody see this too?
> > >
> > > create table t1(i1 int4);
> > > create table t2(i1 int4);
> > > create table t3(i2 int4);
> > >
> > > test=> create rule rm_t1 as on delete to t1
> > > test-> do ( delete from t2 where old.i1 = i1;
> > > test-> delete from t3 where old.i1 = i2;);
> > > pqReadData() -- backend closed the channel unexpectedly.
> > > This probably means the backend terminated abnormally before or
> > > while processing the request.
> > > We have lost the connection to the backend, so further processing is
> > > impossible. Terminating.
> > >
> > >
> > > OS = Linux 2.0.35, gcc 2.7.2.3, postgreSQL-6.4.2
> >
> > That's courios. I can't reproduce it with v6.4 or v6.4.2
> > (Linux 2.1.88, gcc 2.7.2.1). Did the checks with the release
> > tarballs, not with the REL_6_4 tree (will check that later).
>
> CASSERT is off?

Yepp - thanks.

Fixed in REL6_4 and CURRENT.

Placed a patch in

ftp://hub.org/pub/patches/multi_action_rule.patch

Now have to look who damaged the parser in CURRENT not any
longer accepting parentheses for mutiple action rules.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #