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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Robert Haas <robertmhaas(at)gmail(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 20:57:58
Message-ID: 201002202057.o1KKvwK03563@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> I would have said that some time ago, except that I think we have a
> >> "must fix" issue here: isn't pg_upgrade broken for any database
> >> containing plpgsql? A decent solution for that probably will allow
> >> something to fall out for the regression test problem too.
>
> > Uh, well, I added this to pg_dump.c for 9.0:
>
> That's a crock that needs to go away ASAP.

Well, it works, so you are going to need to explain it.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-02-20 21:19:49 Re: Using views for row-level access control is leaky
Previous Message Tom Lane 2010-02-20 20:45:19 Re: PGXS: REGRESS_OPTS=--load-language=plpgsql