| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Jack Flak <jack(at)flak(dot)nospam(dot)org> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: restore/dup OIDs HELP! |
| Date: | 2003-01-11 05:53:42 |
| Message-ID: | 20030110213823.W17716-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 9 Jan 2003, Jack Flak wrote:
> Stephan,
>
> That's very interesting! I didn't even know about these other "hidden"
> fields. How many others are there?
Let's see, I think the set is
ctid, oid, xmin, cmin, xmax, cmax, tableoid
IIRC,
ctid is basically like a physical pointer to where the row actually is
oid you know
xmin - transaction that made the row
cmin - command counter in that transaction that made the row
xmax, cmax - like xmin, cmin but for the transaction that removes it
tableoid - which table it belongs to (for inheritance)
Cmin and xmax share storage, and it looks like xmin/xmax are of a type
that you can't actually do much with from an SQL statement.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah. | 2003-01-11 06:58:53 | is it postgres issue? |
| Previous Message | Bruce Momjian | 2003-01-10 21:10:18 | Re: Encrypted Passwords |