| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Kapil Tilwani <karan_pg_2(at)yahoo(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: OIDs |
| Date: | 2001-06-30 16:23:20 |
| Message-ID: | Pine.LNX.4.30.0106301820030.880-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kapil Tilwani writes:
> What happens when OIDs overflow?
You might get spurious problems when you are altering your schema (unique
contraint violations on the system catalogs), but those can be overcome by
manually advancing the oid past the area used by the system.
> What are XIDs?
transaction ids
> What if they overflow?
Your database system evaporates. Seriously.
> Secondly, OIDs are always sequential, right? Cant they be random....
That would be significantly harder to keep track of.
> I wouldnt like to keep a track (or from anyone finding out) which record came in first...
That wouldn't be very hard to find out without the oids either.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric G. Miller | 2001-06-30 19:07:30 | Re: about PostgreSQL...(important) |
| Previous Message | Tom Lane | 2001-06-30 15:02:57 | Re: User defined type with text* field |