Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Trouble with COPY IN

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Matthew Wakeling <matthew(at)flymine(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Maciek Sakrejda <msakrejda(at)truviso(dot)com>, Samuel Gendler <sgendler(at)ideasculptor(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [HACKERS] Trouble with COPY IN
Date: 2010-07-23 13:32:08
Message-ID: 4C4999D8.705@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc

Kris Jurka wrote:
>>
>> I guess the obvious question is whether we shouldn't instead change
>> the docs to match the behavior. I suspect there's almost no chance
>> we'd consider back-patching a change of this type, since it is a clear
>> behavior change. And even if we did, there would still be people
>> running servers with the old behavior with which JDBC and other
>> drivers would have to cope. Having two different behaviors might be
>> worse than the status quo.
>>
>
> It is a clear behavior change, but that's what bug fixes are.

That was my first reaction. I don't think we're in the business if 
redefining bugs out of existence.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-07-23 13:36:52
Subject: Re: security label support, part.2
Previous:From: Kris JurkaDate: 2010-07-23 13:23:55
Subject: Re: [HACKERS] Trouble with COPY IN

pgsql-jdbc by date

Next:From: Tom LaneDate: 2010-07-23 13:40:35
Subject: Re: [HACKERS] Trouble with COPY IN
Previous:From: Kris JurkaDate: 2010-07-23 13:23:55
Subject: Re: [HACKERS] Trouble with COPY IN

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group