| From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
|---|---|
| To: | Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: AW: [HACKERS] Fwd: Joins and links |
| Date: | 1999-07-06 11:26:18 |
| Message-ID: | 3781E7DA.2F66A759@krs.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zeugswetter Andreas IZ5 wrote:
>
> I think the best compromise would be to have ctid in the where clause.
And we told about this a days ago, but no one did it.
> This would need to always be considered as best path by the optimizer.
> Then the situation is similar to a primary key foreign key scenario.
>
> The referenced table does not need an index, since we know the physical
> position of the row we want (where ctid='(5,255)').
>
> What we need second is an update trigger for the referenced table that
> updates old.ctid to new.ctid in the referencing table. For this to be
Triggers are not fired by vacuum...
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leon | 1999-07-06 11:36:57 | Re[2]: [HACKERS] Fwd: Joins and links |
| Previous Message | Vadim Mikheev | 1999-07-06 11:12:29 | Re: [HACKERS] Fwd: Joins and links |