| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: currtid_byreloid and currtid_byrelname |
| Date: | 2007-06-15 22:57:17 |
| Message-ID: | 4673194D.7050501@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
> In utils/adt/tid.c, there's two mysterious functions with no comments,
> and no-one calling them inside backend code AFAICT: currtid_byreloid
> and currtid_byrelname. What do they do/did?
>
If you have a look at the CVS annotations (
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/tid.c?annotate=1.57
) you can see that they were introduced at version 1.12 (
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/tid.c.diff?r1=1.11;r2=1.12;f=h
)
which has the comment:
The 1st step to implement new type of scan,TidScan.
Now WHERE restriction on ctid is allowed though it is
sequentially scanned.
I often find I have to do this sort of digging to understand what's going on (or find a guilty party :-) ).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-06-15 23:05:51 | Re: currtid_byreloid and currtid_byrelname |
| Previous Message | mark | 2007-06-15 22:31:06 | Re: Change sort order on UUIDs? |