From: | Sam Son <sam89(dot)g(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Muhammad Usman Khan <usman(dot)k(at)bitnine(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Issue with Restore dump with plpythonu, plpython3u installed on postgres16 |
Date: | 2024-09-04 17:46:50 |
Message-ID: | CACW-z_W2cf9O4ZJyPLYugBatBf3SDpQTPj2JSGD-9C8VH8N9ZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian,
Thanks for your suggestions. I will try your modifications and do
benchmarking.
Thanks,
Samson G
On Wed, Sep 4, 2024 at 8:34 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 9/4/24 03:48, Sam Son wrote:
> > Hi Adrian, Muhammad,
> >
> > Thanks for the quick response.
> >
> > For new I cannot do changes in old version DB, since it is deployed
> > remotely and i dont have any access. And it has to be done from multiple
> > servers.
> >
> > As a work around I tried two solutions.
>
> Both of which depend on the plpythonu functions running with plpython3u,
> in other words that they are Python3 compatible. Have you verified that?
>
> >
> > *Solution 1:*
> >
> > After downloading and extracting the dump, convert the pgdump file to
> > sql file which is editable.
> >
> > * pg_restore -f out_dump.sql dump.pgdump*
> >
> > Replace all the plpythonu references with plputhon3u.
> >
> > Restore using the sql file.
> >
> > * sudo -H -u postgres psql -p 5433 -d db_name < out_dump.sql*
>
> I would suggest working on the schema portion separate from the data:
>
> pg_restore -s -f out_dump_schema.sql dump.pgdump*
>
> Do your search and replace, restore to database and then:
>
> pg_restore -a ... dump.pgdump*
>
> Where -a is data only.
>
> In fact if you have control of the pg_dump break it into two parts:
>
> pg_dump -s ... --schema
>
> pg_dump -a ... --data only
>
> >
> >
> > *Solution 2:*
> >
> > After downloading and extracting the dump, get the list of items in dump
> > (Schemas, tables, table data, Index, functions, etc).
> >
> > * pg_restore -l dump.pgdump > dump.txt*
> >
> > Delete all the function references which have plpython3u.
>
> I'm guessing you meant plpythonu above.
>
>
> > *Question:*
> >
> > Our database size is 500GB,
> >
> > Do we see any performance impact using solution 1. Since solution 1 is
> > using sql file load and solution 2 is using pg_restore directly.
> >
> > Kindly recommend what to choose, solution 1 or solution 2 or any other
> > workaround to restore.
>
> Personally I would go with solution 1 with the modifications I suggested.
>
> >
> >
> > Thanks,
> > Samson G
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-09-04 22:20:53 | Re: Issue with Restore dump with plpythonu, plpython3u installed on postgres16 |
Previous Message | Adrian Klaver | 2024-09-04 15:04:45 | Re: Issue with Restore dump with plpythonu, plpython3u installed on postgres16 |