| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Duplicate primary keys/rows |
| Date: | 2005-10-10 22:32:28 |
| Message-ID: | 6694.1128983548@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Mon, Oct 10, 2005 at 05:28:17PM -0400, Tom Lane wrote:
>> But people were a bit worried about what
>> might break.
> In catalog/heap.c there already is a SystemAttributeByName() to do the
> legwork. Seems to me all you'd need to do is check just as you're about
> to fail on "attribute not found".
We could certainly make it work as far as the backend is concerned.
The issue is whether there is any client code out there that will fail
if these entries are no longer present in pg_attribute.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-10-10 23:41:42 | Re: Oracle buys Innobase |
| Previous Message | Martijn van Oosterhout | 2005-10-10 22:15:27 | Re: Duplicate primary keys/rows |