| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dmitry Molotkov <aldarund(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15446: Crash on ALTER TABLE |
| Date: | 2019-01-05 17:09:40 |
| Message-ID: | 20190105170940.2qrbilpxmmxyf4tr@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2019-01-05 12:11:45 +0000, Dean Rasheed wrote:
> It looks like the problem was introduced in PG11 by 16828d5c02 (Fast
> ALTER TABLE ADD COLUMN with a non-NULL default). The first ALTER TABLE
> adds a new column with a non-null default, setting atthasmissing and
> attmissingval. Then the second ALTER TABLE changes the type of the new
> column, but it fails to update attmissingval to match, and thus it
> falls over when trying to re-open the relation because the value in
> attmissingval is no longer compatible with the attribute type.
Paging Dr Dunstan.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-01-06 16:26:04 | BUG #15577: Query returns different results when executed multiple times |
| Previous Message | Phil Hildebrand | 2019-01-05 15:11:57 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-05 17:30:34 | Re: [proposal] Add an option for returning SQLSTATE in psql error message |
| Previous Message | Alvaro Herrera | 2019-01-05 15:42:47 | Re: Use atexit() in initdb and pg_basebackup |