Re: On-disk Tuple Size - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: On-disk Tuple Size
Date
Msg-id 05db01c1e938$6085b3e0$8001a8c0@jester
Whole thread Raw
In response to Re: On-disk Tuple Size  (Curt Sampson <cjs@cynic.net>)
List pgsql-hackers
> Having per-transaction command IDs might allow us to reduce the
range of
> the t_cmin and t_cmax fields. Unfortunately, probably by not all
that
> much, since one doesn't want to limit the number of commands within
a
> single transaction to something as silly as 65536.

If you can figure out how to make that roll over sure, but thats a
very small number.

Consider users who do most of their stuff via functions (one
transaction).  Now consider the function that builds reports, stats,
etc. for some department.  It's likley these work on a per account
basis.

We have a function making invoices that would wrap around that atleast
10x.



pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Documentation on page files
Next
From: Tom Lane
Date:
Subject: Re: On-disk Tuple Size