Re: PGXS: REGRESS_OPTS=--load-language=plpgsql

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, David Fetter <david(at)fetter(dot)org>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
Date: 2010-02-20 23:52:54
Message-ID: 7F8BDDE7-9A26-441B-AE60-DFCCDAD9FC14@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Feb 20, 2010, at 15:03, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Well, I'm willing to implement CREATE OR REPLACE LANGUAGE if people
> are agreed that that's a reasonable fix. I'm slightly worried about
> the restore-could-change-ownership issue, but I think that's much less
> likely to cause problems than embedding special cases for plpgsql in a
> pile of places that we'll never find again.

Just throwing this out there: would a syntax such as CREATE OF NOT
EXISTS, a complement to DROP IF EXISTS, avoid the permissions issue?
And if so, would that be a syntax we'd want to accept in general?
Could the be a CREATE IF NOT EXISTS TABLE?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2010-02-20 23:55:47 Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
Previous Message David Christensen 2010-02-20 23:42:53 Re: PGXS: REGRESS_OPTS=--load-language=plpgsql