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

Re: [HACKERS] Trouble with COPY IN

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Kris Jurka <books(at)ejurka(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:40:37
Message-ID: AANLkTimPUT97D0ErZ_XvTRbVsYjNC0LPQAgQNB0fGaY5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
On Fri, Jul 23, 2010 at 9:32 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> 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.

I certainly understand that reaction - I just worry that there might
be people depending on the current behavior.  We really don't want to
get a reputation for breaking things in minor releases.  But this is
not an area of the code I'm very familiar with, and I'm not in a good
position to judge the likelihood of breakage, so I'll defer to those
who are...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

pgsql-hackers by date

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

pgsql-jdbc by date

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

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