Re: [HACKERS] Small patches in copy.c and trigger.c - Mailing list pgsql-hackers

From jwieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] Small patches in copy.c and trigger.c
Date
Msg-id m107fjh-000EBPC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] Small patches in copy.c and trigger.c  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Small patches in copy.c and trigger.c
List pgsql-hackers
>
> > Bruce Momjian <maillist@candle.pha.pa.us> writes:
> > > I have a morbid curiosity, so I decided to find out how this got into
> > > the source.  On November 1, 1998, Magus applied a patch:
> > >   Here is a first patch to cleanup the backend side of libpq.
> > > Several users have complained about 6.4.* COPY slowing down when loading
> > > rows.  This may be the cause.  Good job finding it.
> >
> > I thought Magnus' changes were only in the current CVS branch, not
> > in REL6_4 ?
>
> You are absolutely right.  Sorry Magnus.  The COPY complaint I heard
> obviously was not from this.
>

    If we don't discover any errors on COPY FROM after some days,
    I think I should fix it in REL6_4 too.

    Do we plan to release v6.4.3 sometimes? If so, are there  any
    neat things I could add to the v6.4.3 feature patch?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] trouble with rules
Next
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] Backend problem with large objects