| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Test to dump and restore objects left behind by regression |
| Date: | 2024-02-22 10:20:29 |
| Message-ID: | 25faa939-df27-4327-a7a3-fc7d3014f522@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.02.24 11:00, Daniel Gustafsson wrote:
>> On 22 Feb 2024, at 10:55, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
>> On Thu, Feb 22, 2024 at 3:03 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> Somebody looking for dump/restore tests wouldn't search
>> src/bin/pg_upgrade, I think.
>
> Quite possibly not, but pg_upgrade is already today an important testsuite for
> testing pg_dump in binary-upgrade mode so maybe more developers touching
> pg_dump should?
Yeah, I think attaching this to the existing pg_upgrade test would be a
good idea. Not only would it save test run time, it would probably also
reduce code duplication.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2024-02-22 10:31:34 | Re: Synchronizing slots from primary to standby |
| Previous Message | Bertrand Drouvot | 2024-02-22 10:14:36 | Re: Synchronizing slots from primary to standby |