Re: Re: making write location work (was: Efficient transaction-controlled synchronous replication)

From: Joseph Conway <mail(at)joeconway(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: simon(at)2ndQuadrant(dot)com, robertmhaas(at)gmail(dot)com, masao(dot)fujii(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: making write location work (was: Efficient transaction-controlled synchronous replication)
Date: 2011-03-24 15:45:58
Message-ID: 4D8B6736.7070600@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/24/11 8:16 AM, Kevin Grittner wrote:
> Simon Riggs wrote:
>> Robert Haas wrote:
>
>>> At least as I understand it, it's not our project policy to carry
>>> around code that doesn't accomplish anything useful. I have no
>>> objection to keeping the field; I simply think that if we're
>>> going to have it, we should make it work
>
>> What a stupid conversation.
>
> That hardly seems like a convincing response. Adding a column to a
> view when the column contains meaninful values seems less likely to
> break things than initially adding it with a different value,
> identical to another column, and then changing the semantics.
>
> +1 for either dropping it or making it work.

+1

Joe

--
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & 24x7 Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ross J. Reedstrom 2011-03-24 16:07:40 Re: [COMMITTERS] pgsql: Document the all-balls IPv6 address.
Previous Message Tom Lane 2011-03-24 15:05:57 Re: Re: making write location work (was: Efficient transaction-controlled synchronous replication)