From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | DeJuan Jackson <djackson(at)speedfc(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [GENERAL] INSTEAD rule bug? |
Date: | 2003-07-21 20:01:03 |
Message-ID: | 18691.1058817663@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
DeJuan Jackson <djackson(at)speedfc(dot)com> writes:
> Or is it simply any conditional rule using UNION/EXCEPT/INTERSECT/...?
Yeah, that's about the size of it :-(. Note though that you could
probably work around the problem by pushing the UNION etc. down into a
sub-select:
SELECT * FROM (SELECT ... UNION ...) foo;
At some point we could look at automatically transforming the query in
that way, but I'm not planning to worry about it now.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-07-21 20:52:41 | Re: [GENERAL] Backwards index scan |
Previous Message | Boris Folgmann | 2003-07-21 19:30:45 | Silent deadlock |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-07-21 20:52:41 | Re: [GENERAL] Backwards index scan |
Previous Message | Bruce Momjian | 2003-07-21 19:57:33 | Re: Fw: Is SQL silly as an RDBMS<->app interface? |