Re: Another idea for dealing with cmin/cmax

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org, heikki(at)enterprisedb(dot)com
Subject: Re: Another idea for dealing with cmin/cmax
Date: 2006-10-02 05:30:16
Message-ID: 27796.1159767016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> ... place a limit on the number of transactions that can be live in a table
> at once.

Urk, well maybe, but ...

> you could shrink all the visibility info to 1 byte if you
> wanted to.

... 256 of 'em is surely not an acceptable limit.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-10-02 05:34:27 Re: src/tools/msvc usage instructions
Previous Message Jim C. Nasby 2006-10-02 05:21:21 Re: Another idea for dealing with cmin/cmax