From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: More nuclear options |
Date: | 2006-07-11 18:50:41 |
Message-ID: | b42b73150607111150l529ddb53nc02888d6ff2adc12@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/10/06, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> All,
> userlock (Merlin)
Ok, I will update the project description and maintain it. userlock
is a great feature, and I tried contacting the original author to get
him to relicense the project but could never get a hold of him. To be
honest, the current userlock contrib module is just very thin wrappers
over backend functions with little/no actual value. I think the user
lock functality really belongs in the core project somehow.
The other proposed features to userlock, namely enhancement to certain
aspects of how they are handled in the backend were largely taken care
of by tom for postgresql 8.1.
By the way, some time back I started another project on gborg,
postisam, but never received permission from my former employer to
release the code. so if that is still there it can be nuked as well.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Mair | 2006-07-11 19:19:28 | newbie patch-attempt: selecting large result sets in psql |
Previous Message | Greg Sabino Mullane | 2006-07-11 18:28:31 | Re: pgsql-patches considered harmful |