| From: | Bo Lorentsen <bl(at)netgroup(dot)dk> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: OID Usage |
| Date: | 2005-01-15 18:10:48 |
| Message-ID: | 41E95CA8.1@netgroup.dk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout wrote:
>But where in the documentation did you see anything saying that they
>were unique? I imagine you just inferred that from somewhere. I'm not
>sure where the documentation should be changed since nowhere actually
>recommends them in any way.
>
>
Hmm, how about as a comment near by the PGoidValue function ?
>Using the CTID, which locates the physical tuple as (block,num). When
>you update a tuple, or vacuum moves it its CTID will change, so it's
>not terribly useful from a user's point of view.
>
>
Hmm, so a data row update also update the CTID in all indexes, too. I
see what you mean !
>Hope this helps,
>
>
It did, thanks.
/BL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-01-15 18:15:36 | Re: Pgsql taking a *lot* of CPU time (unkillable). |
| Previous Message | Bo Lorentsen | 2005-01-15 18:03:43 | Index optimization ? |