| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: pg_dump with tables created in schemas created by extensions |
| Date: | 2016-08-25 11:10:39 |
| Message-ID: | CAB7nPqR12Re9Ai8xvi-aq61-MiWJiNN-F89zue8Z73gM0-cQSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 25, 2016 at 10:25 AM, Martín Marqués <martin(at)2ndquadrant(dot)com> wrote:
> 2016-08-24 21:34 GMT-03:00 Michael Paquier <michael(dot)paquier(at)gmail(dot)com>:
>>
>> Yes, you are right. If I look at the diffs this morning I am seeing
>> the ACLs being dumped for this aggregate. So we could just fix the
>> test and be done with it. I did not imagine the index issue though,
>> and this is broken for some time, so that's not exclusive to 9.6 :)
>
> Do you see any easier way than what I mentioned earlier (adding a
> selectDumpableIndex() function) to fix the index dumping issue?
Yes, we are going to need something across those lines. And my guess
is that this is going to be rather close to getOwnedSeqs() in terms of
logic.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerdan Rezende dos Santos | 2016-08-25 11:34:50 | Re: \timing interval |
| Previous Message | amul sul | 2016-08-25 10:26:39 | Re: Bug in to_timestamp(). |