| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE .. ALTER COLUMN .. ERROR: attribute .. has wrong type |
| Date: | 2017-01-03 19:32:36 |
| Message-ID: | 28476.1483471956@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
>>>> I can cause the error at will on the existing table,
That's good news, at least.
1. Please trigger it with "\set VERBOSITY verbose" enabled, so we can see
the exact source location --- there are a couple of instances of that
text.
2. Even better would be a stack trace for the call to errfinish,
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
3. It's pretty hard to see how you'd reach any of these places for an
ALTER COLUMN TYPE on a simple table. Has the table got rules, triggers,
default values? Could we see "\d+" output for it?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-01-03 19:39:03 | Re: Logical Replication WIP |
| Previous Message | Peter Eisentraut | 2017-01-03 19:17:18 | Re: emergency outage requiring database restart |