Horton

Re: Remove xmin and cmin from frozen tuples

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org, ITAGAKI Takahiro <itagaki.takahiro@lab.ntt.co.jp>
Date: 2005-09-02T20:44:53Z
Lists: pgsql-hackers 
On Fri, Sep 02, 2005 at 04:27:59PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:

> >> Contrariwise, it doesn't really matter (I think) if there are WAL-logged
> >> records already in the table and COPY is adding more that aren't logged.
> 
> > Only if the page is locked in a fashion that the bulk loader can't
> > insert tuples into a page that the other transaction is using.
> 
> What other transaction?  The point I was making is that
> 	BEGIN;
> 	CREATE TABLE ...
> 	INSERT ...
> 	COPY ...
> is still optimizable.  There isn't going to be anyone competing with
> the COPY while it runs.

Sure.  I was thinking that you were looking for a mechanism to relax the
other restriction.

-- 
Alvaro Herrera -- Valdivia, Chile         Architect, www.EnterpriseDB.com
Dios hizo a Adán, pero fue Eva quien lo hizo hombre.