| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, 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:18:04 |
| Message-ID: | 4B806DAC.60704@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
>
> IMO, the non-ugly kludges are (1) implement CREATE OR REPLACE LANGUAGE
> and (2) revert the original patch. Do you want to do one of those
> (which?) or do you have another idea?
>
>
>
I thought we seemed to be converging on some agreement on CREATE OR
REPLACE LANGUAGE.
If not, let me add my vote for that.
I also think we need to state explicitly that module authors can not
expect build files to be version ignorant and always work. Even if we do
something that handles this particular issue, that is likely to be a
happy coincidence rather than something that can be expected all the
time. People need to expect to have to do version-dependent things.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-02-20 23:18:53 | Re: scheduler in core |
| Previous Message | Bruce Momjian | 2010-02-20 23:16:47 | Re: PGXS: REGRESS_OPTS=--load-language=plpgsql |