From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | josh(at)agliodbs(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ams(at)oryx(dot)com |
Subject: | Re: Ding-dong, contrib is dead ... |
Date: | 2006-09-05 19:25:19 |
Message-ID: | b42b73150609051225p46238f8dqdbfb3329cd186086@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/5/06, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> So userlocks will be in pgFoundry for the next rev -- frankly, it should
> have been for 8.1 but I forgot it. For the 8.3 version, as Tom has
> indicated we may want to change the API somewhat anyway, so we'll want the
> pgFoundry version for backwards-compat.
well, I'm confused now. Tom said that cleaned up functions might be
sneaked into 8.2, which is what prompted my question. If that's the
case I'm considering putting something together quickly. It's no big
deal to me either way really. However, it would really be a shame to
drop the contrib module and leave 8.2 without a way of easily use them
(userlocks being, imho, the #1 greatest undiscovered feature in pg).
To be honest, I don't see the need for a backwards-compat version at
all, because all you need to do is copy and paste the code from 8.1.
If advisory functions are promoted in core (8.3 or no), sql wrappers
for compatibility would be trivial to implement. These are one line
wrappers here.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew - Supernews | 2006-09-05 19:25:57 | Re: Ding-dong, contrib is dead ... |
Previous Message | Tom Lane | 2006-09-05 19:19:40 | Re: [HACKERS] Gen_fmgrtab.sh fails with LANG=et_EE |