Re: Fast COPY after TRUNCATE bug and fix - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: Fast COPY after TRUNCATE bug and fix
Date
Msg-id 200703011336.l21Dadr18278@momjian.us
Whole thread Raw
In response to Re: Fast COPY after TRUNCATE bug and fix  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Fast COPY after TRUNCATE bug and fix  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: lo_truncate
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Deadlock with pg_dump?