| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tim Barnard" <tbarnard(at)povn(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Re: [SQL] maximum number of rows in table - what about oid limits? |
| Date: | 2001-06-08 14:41:22 |
| Message-ID: | 9576.992011282@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
"Tim Barnard" <tbarnard(at)povn(dot)com> writes:
> <snip>
> If it does happen, you can just retry the failed object-creation
> command until you get a nonconflicting OID assignment.
> <snip>
> Tom, or anyone who'd know for that matter, what is the
> exact error I would need to look for?
It'd be a complaint about attempt to insert a duplicate key into
the unique index on one of several system catalogs' OID columns.
There wouldn't be any earlier detection of the problem than that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Allan Kamau | 2001-06-08 14:43:59 | Re: Writing transactions in plpgsql |
| Previous Message | Tom Lane | 2001-06-08 14:38:02 | Re: maximum number of rows in table - what about oid limits? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-08 14:53:05 | Re: behavior of ' = NULL' vs. MySQL vs. Standards |
| Previous Message | Tom Lane | 2001-06-08 14:38:02 | Re: maximum number of rows in table - what about oid limits? |