| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints |
| Date: | 2025-03-12 08:27:35 |
| Message-ID: | CAExHW5s-56+JEajW=DqD1ivDE3sD9UHfL2vm2A34qPxiChSm5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 11, 2025 at 3:46 PM Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> wrote:
>>
>> > JFYI, I can reproduce the failure Ashutosh Bapat reported, while
>> > running the pg_upgrade test through meson commands. I am
>> > investigating that further.
>>
>> Ah good, thanks.
>
>
> Somehow, I am now not able to reproduce after the clean build. Yesterday
> I was able to reproduce, so I was happy, but again trying to analyze the issue
> when I start with the
If the test passes for you, can you please try the patches at [1] on
top of your patches? Please apply those, set and export environment
variable PG_TEST_EXTRA=regress_dump_test, and run 002_pg_upgrade test?
I intended to do this but can not do it since the test always fails
with your patches applied.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2025-03-12 08:57:25 | Re: Special-case executor expression steps for common combinations |
| Previous Message | Jim Jones | 2025-03-12 08:25:58 | Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row |