pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i
4+ messages / 3 participants
[nested] [flat]

Commits from this thread:
  2020-03-18 c2c2e531e7  Doc: remove reference to nonexisting GUC from 9.5 release notes.
* BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i
@ 2020-03-18 12:12 PG Bug reporting form <noreply@postgresql.org>
  2020-03-18 12:49 ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i Daniel Gustafsson <daniel@yesql.se>
  0 siblings, 1 reply; 4+ messages in thread

From: PG Bug reporting form @ 2020-03-18 12:12 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: chandu_munnu@yahoo.com

The following bug has been logged on the website:

Bug reference:      16308
Logged by:          Chandra
Email address:      chandu_munnu@yahoo.com
PostgreSQL version: 9.5.15
Operating system:   Linux
Description:        

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;



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i
  2020-03-18 12:12 BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i PG Bug reporting form <noreply@postgresql.org>
@ 2020-03-18 12:49 ` Daniel Gustafsson <daniel@yesql.se>
  2020-03-18 14:20   ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Daniel Gustafsson @ 2020-03-18 12:49 UTC (permalink / raw)
  To: chandu_munnu@yahoo.com; pgsql-bugs@lists.postgresql.org

> On 18 Mar 2020, at 13:12, PG Bug reporting form <noreply@postgresql.org> wrote:
> 
> The following bug has been logged on the website:
> 
> Bug reference:      16308
> Logged by:          Chandra
> Email address:      chandu_munnu@yahoo.com
> PostgreSQL version: 9.5.15
> Operating system:   Linux
> Description:        
> 
> 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.

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.

cheers ./daniel

Attachments: download all (2 files, .tar.gz)

nonexisting_guc_94.patch (application/octet-stream, 1.1K) download From 77a95e2a592a813cf82314a469072a0a3efbb6fc Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson <daniel@yesql.se> Date: Wed, 18 Mar 2020 13:43:21 +0100 Subject: [PATCH] Remove reference to nonexisting GUC from release notes Commit dbe405b7859c68a4927afd8334059cf9348afbeb added a set of GUCS as PGDLLIMPORT, but idle_in_transaction_session_timeout is only in 9.6 and onwards (which is reflected in the commit message), so the reference to the change in the release notes is a bit broad. --- doc/src/sgml/release-9.4.sgml | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml index 179243a35f..cb80a04661 100644 --- a/doc/src/sgml/release-9.4.sgml +++ b/doc/src/sgml/release-9.4.sgml @@ -582,7 +582,6 @@ Branch: REL9_4_STABLE [dbe405b78] 2020-01-21 13:47:17 +0900 <para> This applies to - <literal>idle_in_transaction_session_timeout</literal>, <literal>lock_timeout</literal>, <literal>statement_timeout</literal>, <literal>track_activities</literal>, -- 2.21.1 (Apple Git-122.3) =
nonexisting_guc_95.patch (application/octet-stream, 1.1K) download From 8101b5aa582a8f8522ff3d2506e11df71aabb4d0 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson <daniel@yesql.se> Date: Wed, 18 Mar 2020 13:39:41 +0100 Subject: [PATCH] Remove reference to nonexisting GUC from release notes Commit 4a49149b9d74d2f9479cb73227e9646c901c84e6 added a set of GUCS as PGDLLIMPORT, but idle_in_transaction_session_timeout is only in 9.6 and onwards (which is reflected in the commit message), so the reference to the change in the release notes is a bit broad. --- doc/src/sgml/release-9.5.sgml | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml index ab213c847e..15f2cabd52 100644 --- a/doc/src/sgml/release-9.5.sgml +++ b/doc/src/sgml/release-9.5.sgml @@ -593,7 +593,6 @@ Branch: REL9_4_STABLE [dbe405b78] 2020-01-21 13:47:17 +0900 <para> This applies to - <literal>idle_in_transaction_session_timeout</literal>, <literal>lock_timeout</literal>, <literal>statement_timeout</literal>, <literal>track_activities</literal>, -- 2.21.1 (Apple Git-122.3) =
^ permalink raw reply [nested|flat] 4+ messages in thread

* Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i
  2020-03-18 12:12 BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i PG Bug reporting form <noreply@postgresql.org>
  2020-03-18 12:49 ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i Daniel Gustafsson <daniel@yesql.se>
@ 2020-03-18 14:20   ` Tom Lane <tgl@sss.pgh.pa.us>
  2020-03-18 15:07     ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i Daniel Gustafsson <daniel@yesql.se>
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2020-03-18 14:20 UTC (permalink / raw)
  To: Daniel Gustafsson <daniel@yesql.se>; +Cc: chandu_munnu@yahoo.com; pgsql-bugs@lists.postgresql.org

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





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i
  2020-03-18 12:12 BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i PG Bug reporting form <noreply@postgresql.org>
  2020-03-18 12:49 ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i Daniel Gustafsson <daniel@yesql.se>
  2020-03-18 14:20   ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-03-18 15:07     ` Daniel Gustafsson <daniel@yesql.se>
  0 siblings, 0 replies; 4+ messages in thread

From: Daniel Gustafsson @ 2020-03-18 15:07 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: chandu_munnu@yahoo.com; pgsql-bugs@lists.postgresql.org

> On 18 Mar 2020, at 15:20, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:

>> 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).

Doh, of course, my internal EOL clock hasn't been reconfigured it seems. Thanks.

cheers ./daniel




^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2020-03-18 15:07 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-03-18 12:12 BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i PG Bug reporting form <noreply@postgresql.org>
2020-03-18 12:49 ` Daniel Gustafsson <daniel@yesql.se>
2020-03-18 14:20   ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i Tom Lane <tgl@sss.pgh.pa.us>
2020-03-18 15:07     ` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i Daniel Gustafsson <daniel@yesql.se>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox