Re: pg_rewind, a tool for resynchronizing an old master after failover - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: pg_rewind, a tool for resynchronizing an old master after failover
Date
Msg-id 51AE58DB.80804@commandprompt.com
Whole thread Raw
In response to Re: pg_rewind, a tool for resynchronizing an old master after failover  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 06/04/2013 01:55 PM, Josh Berkus wrote:

> That seems rather like a catch-22 Bruce.  If they don't check with the
> legal department, it's dangerous, but if they do check, it's dangerous?
>
> Presumably if they checked with the legal department, it's cleared.  We
> should be wary of stuff contributed by company employees who *didn't* check.
>
> This particular tool seems highly unlikely to be legitimately
> patentable, anyway.  There's too much prior art.

"legitimately patentable" is a rather ethereal phrase in our industry 
right now don't you think?

JD

>


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: psql \dv+ shows view size as 0 bytes
Next
From: Tom Lane
Date:
Subject: Re: Improved error message for CREATE EXTENSION patch...