Re: the XID question

From: "Charles(dot)Hou" <givemeegn(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: the XID question
Date: 2011-01-19 14:54:46
Message-ID: b5fc661d-0c4b-4dd9-ab56-06888410188c@m20g2000prc.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 1月19日, 下午10時39分, Kevin(dot)Gritt(dot)(dot)(dot)(at)wicourts(dot)gov ("Kevin Grittner")
wrote:
> Filip Rembia*kowski<plk(dot)zu(dot)(dot)(dot)(at)gmail(dot)com> wrote:
> > 2011/1/19 Charles.Hou <giveme(dot)(dot)(dot)(at)gmail(dot)com>:
> >> " select * from mybook" SQL command also increase the XID ?
>
> > Yes. Single SELECT is a transaction. Hence, it needs a transaction
> > ID.
>
> No, not in recent versions of PostgreSQL.  There's virtual
> transaction ID, too; which is all that's needed unless the
> transaction writes something.
>
my postgresql version is 8.1.3
you means the newer version has a virtual transaction ID. and what's
the maxmium of this virtual id, also 4 billion ?
should i also vacuum freeze the virtual id in the new version when it
reached the 4 billion?

> Also, as a fine point, if you use explicit database transactions
> (with BEGIN or START TRANSACTION) then you normally get one XID for
> the entire transaction, unless you use SAVEPOINTs.
>
> -Kevin
>
> --
> Sent via pgsql-performance mailing list (pgsql-performa(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-performance

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2011-01-19 17:07:24 Re: Running PostgreSQL as fast as possible no matter the consequences
Previous Message Kevin Grittner 2011-01-19 14:39:47 Re: the XID question