Re: [HACKERS] Small patches in copy.c and trigger.c

From: jwieck(at)debis(dot)com (Jan Wieck)
To: phd2(at)earthling(dot)net
Cc: jwieck(at)debis(dot)com, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Small patches in copy.c and trigger.c
Date: 1999-02-02 09:54:04
Message-ID: m107cWy-000EBPC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Hello!
>
> On Mon, 1 Feb 1999, Jan Wieck wrote:
> > I've just committed two very simple patches to copy.c and
> > trigger.c which caused backend to grow until transaction end.
>
> Any chance I will see the patch? Or even better, postgres 6.4.3? Recently I
> got a problem loading db dump...

Must be something different. I've checked v6.4 and v6.4.2,
and the duplicate palloc() for values isn't there. Since
triggers are created after loading the data in any dump, that
one couldn't be it either.

I'll do some memory tests with copy in the released versions
and if I find something, put a patch onto the ftp server.

Jan

--

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 1999-02-02 10:02:00 Re: [HACKERS] READ COMMITTED isolevel is implemented ...
Previous Message Oleg Broytmann 1999-02-02 09:45:34 Re: [HACKERS] Small patches in copy.c and trigger.c