Re: Table Spaces - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Table Spaces
Date
Msg-id 40AB7A8D.4070006@dunslane.net
Whole thread Raw
In response to Re: Table Spaces  (pgsql@mohawksoft.com)
List pgsql-hackers
pgsql@mohawksoft.com wrote:

>>On Wednesday 19 May 2004 00:19, pgsql@mohawksoft.com wrote:
>>    
>>
>>>>pgsql@mohawksoft.com wrote:
>>>>        
>>>>
>>>>>This makes me worried. That's the way we *used* to do things, but the
>>>>>sleazy IP lawyers are looking for anything with which they can create
>>>>>the
>>>>>impression of impropriety. The open source and free projects are
>>>>>          
>>>>>
>>>ground
>>>      
>>>
>>>>>zero for this crap.
>>>>>
>>>>>We *really* need to be careful.
>>>>>          
>>>>>
>>>>I assumed this tool was GPL and we just needed to avoid the GPL issue.
>>>>        
>>>>
>>>I'm probably just being alarmist, but think about some IP lawyer buying
>>>up
>>>the entity that owns the GPL code, and suing end user's of PostgreSQL.
>>>
>>>This is similar to what is happening in Linux land with SCO.
>>>
>>>The best defense is to say, nope, we didn't copy your stuff, we
>>>implemented it ourselves based on the documentation.
>>>      
>>>

The safe bet if we want to use junction points is to use clean room 
techniques. I understand from other comments that it wouldn't be difficult.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal: be smarter about i/o patterns in index scan
Next
From: Tom Lane
Date:
Subject: Re: Rough draft for Unicode-aware UPPER()/LOWER()/INITCAP()