| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kragen Sitaker <kragen+pgsql(at)airwave(dot)com> |
| Cc: | abartley(at)evolvosystems(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Vacuum Error |
| Date: | 2004-01-13 04:43:49 |
| Message-ID: | 7899.1073969029@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kragen Sitaker <kragen+pgsql(at)airwave(dot)com> writes:
> On Mon, Jan 12, 2004 at 06:20:23PM -0500, Tom Lane wrote:
>> No; an OID collision would have occurred when you tried to create a
>> table. If two tables are present in pg_class then they have different
>> OIDs, and shouldn't have any conflicts in pg_statistic.
> How would that OID collision manifest? Do you think the error message
> might look similar?
Similar, but referring to pg_class_oid_index.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-01-13 04:56:27 | Re: Column qualifier issue |
| Previous Message | Greg Stark | 2004-01-13 04:32:15 | Re: Postgres + Xapian (was Re: fulltext searching via a |