Re: pg_restore depending on user functions
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Дмитрий Иванов <firstdismay@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Date: 2021-11-14T17:31:09Z
Lists: pgsql-bugs, pgsql-general
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay@gmail.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
Commits
-
Adjust pg_dump's priority ordering for casts.
- d4f6a36d8265 13.6 landed
- b55f2b692655 15.0 landed
- 69949ea68cf9 12.10 landed
- 54619a25df7c 11.15 landed
- 2b36973d95c6 10.20 landed
- 0fdf67476ccb 14.2 landed