Re: restore/dup OIDs HELP!

From: Jack Flak <jack(at)flak(dot)nospam(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: restore/dup OIDs HELP!
Date: 2003-01-14 22:15:39
Message-ID: f_%U9.1886$qD7.685@newssvr19.news.prodigy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks man; Iappreciate the data.

Stephan Szabo wrote:

>
> 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.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Andrew Biagioni 2003-01-14 23:56:30 Re: Deadlock Checker doesn't see foreign-key locks
Previous Message Vida Luz Arista 2003-01-14 19:41:15 Re: Case Studio Postgresql