From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | eberger(at)gewi(dot)kfunigraz(dot)ac(dot)at (Erich Stamberger) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] trouble with rules |
Date: | 1999-02-02 10:03:47 |
Message-ID: | m107cgN-000EBPC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> 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).
But with the current development tree I get a parse error
near delete!
I recall that there was something done in the parser about
parantheses around queries. Have to check it out and if fixed
add multiple action rules with parantheses to the regression
test to avoid breakage again in the future.
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) #
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-02-02 10:13:40 | Re: [HACKERS] trouble with rules |
Previous Message | Vadim Mikheev | 1999-02-02 10:02:00 | Re: [HACKERS] READ COMMITTED isolevel is implemented ... |