From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: New array functions |
Date: | 2003-08-28 21:44:26 |
Message-ID: | 3F4E77BA.90906@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>
>>I have no objection to removing it now, but previously I think you
>>agreed with Bruce's comment that we should leave it intact (but
>>deprecated) for 7.4, and remove in 7.5.
>
> Did we discuss this already? I'd forgotten.
>
> In any case, the module isn't visibly deprecated at the moment.
> If the idea is to avoid blindsiding its users, then we definitely
> must mark it as slated for removal, and provide some docs about
> how to replace it.
>
I can't find it in the archives for some reason, but here was the exchange:
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>>Joe Conway wrote:
>>
>>>I do agree that it makes contrib/array unnecessary. I was going to
>>>suggest we remove that if this was committed.
>
>>Good idea.
>
> We could do that, but it might be more friendly to just mark it as
> deprecated for one release cycle before zapping it. That'd give
> people who use it some time to convert over.
So I guess since it was actually you who objected, you have the right to
change your mind ;-)
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2003-08-28 22:04:19 | Re: Replication Ideas |
Previous Message | Tom Lane | 2003-08-28 21:37:39 | Re: Nasty problem in hash indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-28 23:04:19 | Re: New array functions |
Previous Message | Joe Conway | 2003-08-28 21:08:52 | Re: New array functions |