From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Fast COPY after TRUNCATE bug and fix |
Date: | 2007-03-01 13:36:39 |
Message-ID: | 200703011336.l21Dadr18278@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Simon Riggs wrote:
> On Wed, 2007-02-28 at 21:09 -0500, Bruce Momjian wrote:
> > Your patch has been added to the PostgreSQL unapplied patches list at:
>
> > Simon Riggs wrote:
> > > It's been pointed out to me that I introduced a bug as part of the
> > > recent optimisation of COPY-after-truncate.
> > >
> > > The attached patch fixes this for me on CVS HEAD. It does this by making
> > > an explicit request for relcache hint cleanup at EOXact and takes a more
> > > cautious approach during RelationCacheInvalidate().
>
> You understand that this fixes a bug in CVS HEAD?
>
> It isn't a new feature.
This is for CVS HEAD only, right? Fixed still go into the queue, but
for a shorter amount of time, hopefully.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-03-01 14:06:41 | Re: [HACKERS] Deadlock with pg_dump? |
Previous Message | Bruce Momjian | 2007-03-01 13:35:21 | Re: lo_truncate |