From: | Thomas Kellerer <shammat(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_restore remap schema |
Date: | 2022-11-16 15:14:39 |
Message-ID: | 5a10c0aa-17c0-865e-b1c4-fcab0a51eeb7@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane schrieb am 08.08.2022 um 20:22:
> Guillaume Lelarge <guillaume(at)lelarge(dot)info> writes:
>> Le lun. 8 août 2022 à 18:28, Fabrice Chapuis <fabrice636861(at)gmail(dot)com> a
>>> Is a development in progress to add this option
>
>> Nope, never heard of someone working on this.
>
> People have asked for such a thing before, but it'd be quite difficult
> to do reliably --- particularly inside function bodies, which aren't
> normally parsed at all during a dump/restore. If you're willing to
> accept a 95% solution, running the pg_restore output through "sed"
> would likely work fairly well. I'd personally want to diff the
> before-and-after scripts before applying though :-)
FWIW Oracle's "remap_schema" for their DataPump tool doesn't do this inside triggers or functions either.
It does not even adjust the schema for sequences used for default values of columns.
So for users migrating from Oracle, this wouldn't be a surprise ;)
From | Date | Subject | |
---|---|---|---|
Next Message | shashidhar Reddy | 2022-11-16 15:55:37 | Re: unrecognized node type: 350 |
Previous Message | Tom Lane | 2022-11-16 15:10:20 | Re: pg_restore remap schema |