Skip site navigation (1) Skip section navigation (2)

pg_dump no longer honors --no-reconnect

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: pg_dump no longer honors --no-reconnect
Date: 2003-09-29 04:43:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
From CVS logs I see:
	pg_dump/pg_restore now always use SET SESSION AUTHORIZATION, not
	\connect, to control object ownership.  The
	use-set-session-authorization and no-reconnect switches are obsolete
	(still accepted on the command line, but they don't do anything).  This
	is a precursor to fixing handling of CREATE SCHEMA, which will be a
	separate commit.

This was to fix a problem with restoring schemas.  However, the commit
says that --use-set-session-authorization and --no-reconnect are no
longer honored.  Seems we can silently ignore a
--use-set-session-authorization flag because that is now the default,
but I don't see how we can ignore a --no-reconnect flag --- we should
throw an error.

The pg_dump manual says:
	    This option is obsolete but still accepted for backwards compatibility. 

Also, the 7.3 manual mentions that only the super-user can restore using
--use-set-session-authorization.  This is now the only way to create
dumps.  Seems this is a new limitation to pg_dump that we didn't

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073


pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2003-09-29 05:05:03
Subject: Re: 2-phase commit
Previous:From: Hiroshi InoueDate: 2003-09-29 04:39:56
Subject: Re: 2-phase commit

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group