Re: Installing PL/pgSQL by default

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Thom Brown <thombrown(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Subject: Re: Installing PL/pgSQL by default
Date: 2009-12-12 04:57:03
Message-ID: 28458.1260593823@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> A more difficult issue is whether we should preserve the fact that
> plpgsql was _removed_ in the pg_dump output, i.e, if someone removes
> plpgsql from a database, do we issue a DROP LANGUAGE in pg_dump? I
> don't remember us having to deal with anything like this before.

The public schema is a precedent.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Willy-Bas Loos 2009-12-12 09:55:05 Re: "setsockopt(TCP_KEEPCNT) failed: Invalid argument" on Debian Lenny
Previous Message Bruce Momjian 2009-12-12 03:35:17 Re: Installing PL/pgSQL by default

Browse pgsql-hackers by date

  From Date Subject
Next Message Ing . Marcos Lui's Orti'z Valmaseda 2009-12-12 06:42:31 Re: SE-PostgreSQL/Lite Review
Previous Message KaiGai Kohei 2009-12-12 04:04:55 Re: Largeobject Access Controls (r2460)