pgsql: Use CREATE OR REPLACE LANGUAGE in pg_dump to avoid the need for a

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use CREATE OR REPLACE LANGUAGE in pg_dump to avoid the need for a
Date: 2010-02-24 01:57:16
Message-ID: 20100224015716.1EABE7541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Use CREATE OR REPLACE LANGUAGE in pg_dump to avoid the need for a couple of
significantly uglier kluges that were working around the change in plpgsql's
preinstalled status.

Modified Files:
--------------
pgsql/src/bin/pg_dump:
pg_dump.c (r1.572 -> r1.573)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.572&r2=1.573)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-02-24 02:15:59 pgsql: Un-break pg_dump for the case of zero-column tables.
Previous Message Tom Lane 2010-02-24 01:35:14 pgsql: Make pg_regress use CREATE OR REPLACE LANGUAGE, so that