From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: test_pg_dump missing cleanup actions |
Date: | 2018-09-04 22:02:51 |
Message-ID: | 20180904220251.GL4184@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > While hacking another patch, I have noticed that triggerring multiple
> > times in a row installcheck on test_pg_dump results in a failure because
> > it is missing clean up actions on the role regress_dump_test_role.
> > Roles are shared objects, so I think that we ought to not let traces of
> > it when doing any regression tests on a running instance.
>
> > Attached is a patch to clean up things.
>
> I'm confused. Isn't the point of that script exactly to create a modified
> extension for testing pg_dump with?
>
> What I'd do is leave the final state as-is and add a "drop role if exists"
> at the start, similar to what some of the core regression tests do.
I've not followed this thread but based on Tom's response, I agree with
his suggestion of what to do here.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2018-09-04 22:06:07 | Re: Bug fix for glibc broke freebsd build in REL_11_STABLE |
Previous Message | Peter Geoghegan | 2018-09-04 21:55:14 | Re: Bug in ginRedoRecompress that causes opaque data on page to be overrun |