| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default |
| Date: | 2021-06-11 22:03:28 |
| Message-ID: | 240c8193-8b3d-9328-8465-806f605dfe91@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 6/11/21 5:59 PM, Andrew Dunstan wrote:
>
> How to ignore something that's got into the catalog that shouldn't be
> there is less clear. At the point where we fetch missing values all we
> have access to is a TupleDesc.
>
>
On further reflection I guess we'll need to make that check at the point
where we fill in the TupleDesc.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-06-12 00:21:47 | Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti |
| Previous Message | Andrew Dunstan | 2021-06-11 21:59:07 | Re: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2021-06-11 22:12:29 | Re: Replication protocol doc fix |
| Previous Message | Andrew Dunstan | 2021-06-11 21:59:07 | Re: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default |