| From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | DiasCosta <diascosta(at)diascosta(dot)org>, Łukasz Jarych <jaryszek(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Cloning schemas |
| Date: | 2018-07-04 22:53:17 |
| Message-ID: | CANu8Fiz29cR-vjOGP3bDHHT0-pVVg1B_UnFAdX+ttMfvaHOkfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 4, 2018 at 6:48 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 07/04/2018 03:38 PM, Melvin Davidson wrote:
>
>>
>>
>> On Wed, Jul 4, 2018 at 2:48 PM, DiasCosta <diascosta(at)diascosta(dot)org
>> <mailto:diascosta(at)diascosta(dot)org>> wrote:
>>
>> Hi Melvin,
>>
>> I'm new to clone_schema.
>> Can I use it on PostgreSQL 9.6?
>>
>> TIA
>> DCostaployment by invitation only!
>>
>>
>> > Can I use it on PostgreSQL 9.6?
>>
>> Yes, but because the developer(s) once again monkeyed with the system
>> catalogs, there are now
>>
>
> Well that is one of the things that distinguish a major release so it
> should be no surprise.
>
>
>
The problem is, AFAICS, none of the changes induced were really necessary
or increased performance.
*Melvin Davidson*
*Maj. Database & Exploration Specialist*
*Universe Exploration Command – UXC*
Employment by invitation only!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-07-04 23:00:42 | Re: Cloning schemas |
| Previous Message | Adrian Klaver | 2018-07-04 22:48:03 | Re: Cloning schemas |