Re: foreign key locks, 2nd attempt

Christopher Browne <cbbrowne@gmail.com>

From: Christopher Browne <cbbrowne@gmail.com>

To: Kevin Grittner <Kevin.Grittner@wicourts.gov>

Cc: Jeroen Vermeulen <jtv@xs4all.nl>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2011-11-10T20:38:41Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Try to avoid running with a full fsync request queue.
- 7f242d880b5b 9.1.0 cited

On Thu, Nov 10, 2011 at 3:29 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Christopher Browne <cbbrowne@gmail.com> wrote:
>
>> There's value in having an "immutability" constraint on a column,
>> where, in effect, you're not allowed to modify the value of the
>> column, once assigned.
>
> +1  We would definitely use such a feature, should it become
> available.

Added to TODO list.
-- 
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"