pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-patches <pgsql-patches@postgresql.org>
Subject: Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Date: Wed, 12 Mar 2008 17:33:47 +0000
Message-ID: <47D813FB.1000006@enterprisedb.com> (raw)
In-Reply-To: <2e78013d0803121026r227bbebdr5189be193b4a1bf5@mail.gmail.com>
References: <47D505AF.4040101@postnewspapers.com.au>
	<47D54DB2.4020405@enterprisedb.com>
	<24304.1205162440@sss.pgh.pa.us>
	<47D67C3F.1030406@enterprisedb.com>
	<5827.1205269597@sss.pgh.pa.us>
	<47D7DE12.80700@enterprisedb.com>
	<2e78013d0803120847k2e8afbedrc39e29e5194d3c6e@mail.gmail.com>
	<19902.1205337439@sss.pgh.pa.us>
	<2e78013d0803121002o2b7a8531y1553ce66cb6d1537@mail.gmail.com>
	<47D80F5C.2060500@enterprisedb.com>
	<2e78013d0803121026r227bbebdr5189be193b4a1bf5@mail.gmail.com>

Pavan Deolasee wrote:
> Wait. Subtransaction ids are local to a transaction and always start from 1.
> See this:
> 
>     /*
>      * reinitialize within-transaction counters
>      */
>     s->subTransactionId = TopSubTransactionId;
>     currentSubTransactionId = TopSubTransactionId;

No, we're not talking about SubTransactionIds. We're talking about real 
XIDs assigned to subtransactions. Subtransactions are assigned regular 
XIDs as well, just like top-level transactions.

I can see where you were coming from with you suggestion now :-).

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com



view thread (30+ messages)  latest in thread

Message-ID: <47D813FB.1000006@enterprisedb.com>
Permalink:  ../47D813FB.1000006@enterprisedb.com/
Also on:    postgresql.org/message-id/47D813FB.1000006@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: heikki@enterprisedb.com, pavan.deolasee@gmail.com, tgl@sss.pgh.pa.us, craig@postnewspapers.com.au, pgsql-patches@postgresql.org
  Subject: Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
  In-Reply-To: <47D813FB.1000006@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox