| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Gray <jgray(at)azuli(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: update db doesnt work |
| Date: | 2002-05-27 16:49:39 |
| Message-ID: | 14023.1022518179@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John Gray <jgray(at)azuli(dot)co(dot)uk> writes:
> On Mon, 2002-05-27 at 16:30, Gregory Seidman wrote:
>> Which, while accurate, fails to answer the answer the question. A column is
>> not being added. A table is not being created. Rows are being updated and
>> the system is complaining that there are too many columns. Why?
> Don't know what the answer is, but it would be interesting to confirm
> whether PG thinks there are only 1600 columns.
Oh, wait, of course. The table has 1600 columns. But an UPDATE
operation needs to form an intermediate tuple containing all 1600
data columns plus the CTID column.
We should allow that, IMHO, which is another reason why heap_formtuple
is not the place to be applying the restriction. Looks like there is
some work to do here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tina Messmann | 2002-05-27 17:00:48 | Re: question about 2 versions and libraries |
| Previous Message | Tom Lane | 2002-05-27 16:31:02 | Re: [meta] news.postgresql.org still down - who do I complain to? |