| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: pg_dump with tables created in schemas created by extensions |
| Date: | 2016-08-23 08:02:27 |
| Message-ID: | CAB7nPqSxgx=wywMbfmV-+0bGqc+03W9KWYCQU=PZVsJ7LvK9Mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Aug 13, 2016 at 6:58 AM, Martín Marqués <martin(at)2ndquadrant(dot)com> wrote:
> I believe the fix will be simple after the back and forth mails with
> Michael, Stephen and Tom. I will work on that later, but preferred to
> have the tests the show the problem which will also make testing the fix
> easier.
>
> Thoughts?
It seems to me that we are going to need a bit more coverage for more
object types depending on the code paths that are being changed. For
example, sequences or functions should be checked for as well, and not
only tables. By the way, do you need help to build a patch or should I
jump in?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-08-23 08:39:43 | Re: pg_receivexlog does not report flush position with --synchronous |
| Previous Message | Petr Jelinek | 2016-08-23 08:02:16 | Re: [PATCH] Transaction traceability - txid_status(bigint) |