| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Wiebe Cazemier <halfgaar(at)gmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Delete rule chain stops unexpectedly |
| Date: | 2005-10-25 18:06:17 |
| Message-ID: | 18659.1130263577@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Wiebe Cazemier <halfgaar(at)gmail(dot)com> writes:
> Tom Lane wrote:
>> Because the rule converts those inserts into, effectively,
>>
>> INSERT INTO debuglog SELECT ... WHERE EXISTS(some matching OLD row);
>>
>> and there are no longer any matching OLD rows in the view.
> Is this behaviour also present in Postgres 7?
It's always been like that. We've jiggered some details about the order
of rule firing, but not much else. If you want a more detailed response
you need to be more specific about what version you're comparing to and
exactly what rules you're worried about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Judith Altamirano Figueroa | 2005-10-25 23:28:38 | backend error |
| Previous Message | Magnus Hagander | 2005-10-25 16:27:44 | Re: 8.0.x windows installer fails? |