Subject: Re: Problems with pg_restore (plpgsql already exists)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <17919563-C079-438C-9702-5A0806127DFD@gmail.com>
Date: Sat, 25 Feb 2012 09:23:50 -0700
Cc: Guillaume Lelarge <guillaume@lelarge.info>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <274BAD81-38BF-4537-B474-ADCDF77E318A@elevated-dev.com>
References: <EB254343-461B-4B6B-93A1-3065BA902CF3@gmail.com>
	<4F4820C8.2000703@iii.com>
	<CAAhXZGv+sU3SksPi-hn2GECf2O_-Xt-xBANgCJyuWDwFiUDnAQ@mail.gmail.com>
	<1330183903.2593.1.camel@localhost.localdomain>
	<17919563-C079-438C-9702-5A0806127DFD@gmail.com>
To: Brian Weaver <cmdrclueless@gmail.com>

On Feb 25, 2012, at 9:18 AM, Brian Weaver wrote:

> Thanks for the pointer. Is it just me that finds it the behavior of =
pg_restore odd? If the default installation since 9.0 has PL/PgSQL =
installed then why does pg_restore still emit statements to create the =
language? As a developer by trade it smells like a bug.=20

It's pg_dump that's emitting the command to create the language. If you =
ran pg_dump from 9.0+, it would not do so. This is an example of why the =
standard advice for upgrading is to use the newer pg_dump against the =
older database--you can often get away without doing that, and I am one =
of those people who often ignores that advice and does things the easier =
way until it breaks, but it is safer.

--=20
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice