| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
| Subject: | Re: pg_restore remap schema |
| Date: | 2022-11-16 14:42:28 |
| Message-ID: | 1340308.1668609748@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Guillaume Lelarge <guillaume(at)lelarge(dot)info> writes:
> Le mer. 16 nov. 2022 à 13:08, Fabrice Chapuis <fabrice636861(at)gmail(dot)com> a
> écrit :
>> I worked on the pg_dump source code to add remap schema functionality to
>> use it internally where I work. This is a first version that allows to
>> remap tables, views and sequences (only to export schema). Is this
>> development likely to interest the PG community and to continue this
>> development further?
> If it doesn't work on functions, that will be a big issue. And to be
> honest, I don't think you can do it reliably on functions, especially with
> dynamic queries in PL/pgsql.
Yeah --- I fear there is no hope of making a feature like this that
works reliably enough that we'd accept it. pg_restore is just not
that smart about what is in the chunks of DDL that it processes,
and trying to make it smart enough is a losing game.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stéphane Tachoires | 2022-11-16 14:58:29 | Re: pg_restore remap schema |
| Previous Message | Tom Lane | 2022-11-16 14:27:57 | Re: unrecognized node type: 350 |