From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_restore depending on user functions |
Date: | 2021-11-14 17:31:09 |
Message-ID: | 2011525.1636911069@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay(at)gmail(dot)com> writes:
> 1. I can determine the dependencies of the custom functions when creating
> the pg_dump? I did not find anything suitable for SUPPORT, probably this is
> not the case?
> To recreate all of the functionality, I had to run schema recovery twice.
> (--schema-only)
Usually this is caused by being careless about search_path assumptions
in your functions ... but with no details, it's impossible to say
anything with certainty.
> 2. Why is pg_restore trying to set the value of fields of type GENERATED
> ALWAYS?
Otherwise it couldn't guarantee that the rows were restored with the same
values of the identity column that they had before. I recall that we
had some bugs with GENERATED ALWAYS in early v10 versions, but when I try
it now, dump/restore of a table with an identity column seems to work
as expected. What minor release are you using?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Дмитрий Иванов | 2021-11-14 18:37:19 | Re: pg_restore depending on user functions |
Previous Message | Дмитрий Иванов | 2021-11-14 10:10:32 | pg_restore depending on user functions |
From | Date | Subject | |
---|---|---|---|
Next Message | Дмитрий Иванов | 2021-11-14 18:37:19 | Re: pg_restore depending on user functions |
Previous Message | Avi Weinberg | 2021-11-14 14:14:47 | Logical Replication - Source and Destination Table Name Not The Same |