| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: cataloguing NOT NULL constraints |
| Date: | 2023-08-31 11:00:00 |
| Message-ID: | ed90a146-5449-0b5e-1cbc-7e48fa8ac3c6@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
31.08.2023 13:26, Alvaro Herrera wrote:
> Hmm, that's some weird code I left there all right. Can you please try
> this patch? (Not final; I'll review it more completely later,
> particularly to add this test case.)
Yes, your patch fixes the issue. I get the same error now:
ERROR: column "a" in child table must be marked NOT NULL
Thank you!
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2023-08-31 11:06:42 | Re: Replace some cstring_to_text to cstring_to_text_with_len |
| Previous Message | Kumar, Sachin | 2023-08-31 10:48:06 | RE: Initial Schema Sync for Logical Replication |