Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i
От | Tom Lane |
---|---|
Тема | Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i |
Дата | |
Msg-id | 941.1584541209@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #16308: pg_restore: [archiver (db)] could not execute query:ERROR: unrecognized configuration parameter "i (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: BUG #16308: pg_restore: [archiver (db)] could not execute query:ERROR: unrecognized configuration parameter "i
|
Список | pgsql-bugs |
Daniel Gustafsson <daniel@yesql.se> writes: > On 18 Mar 2020, at 13:12, PG Bug reporting form <noreply@postgresql.org> wrote: >> pg_restore: [archiver (db)] Error while PROCESSING TOC: >> pg_restore: [archiver (db)] Error from TOC entry 3796; 0 0 SEARCHPATH >> SEARCHPATH >> pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized >> configuration parameter "idle_in_transaction_session_timeout" >> Command was: SET idle_in_transaction_session_timeout = 0; > idle_in_transaction_session_timeout only exist starting with 9.6, so it sounds > like you are restoring a dump made by a newer version of pg_dump. You should > be using the version of pg_dump which match the server version you are > restoring into. Or, if that's the only error you get, you could just ignore it. It's harmless enough, as long as you don't insist on a single-transaction restore. (If you do need that, dump pg_restore's output into a file and remove the offending SET.) > On that note, it seems that the 9.4 and 9.5 release notes reference the GUC in > question, even though the commit message correctly states the GUC is only in > 9.6 and newer. To avoid confusion, I suggest that we remove the reference in > the back-branches as per the attached. My bad, I'll see about fixing that (in 9.5; it's too late for 9.4). regards, tom lane
В списке pgsql-bugs по дате отправления: