Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > The only other
> > unusual case I saw was tid outputing block number as %d and not %u. Is
> > that OK?
>
> Seems like it should use %u. The input side might be wrong too.
>
OK, fixed. Patch attached. There was also some confusi
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The only other
> unusual case I saw was tid outputing block number as %d and not %u. Is
> that OK?
Seems like it should use %u. The input side might be wrong too.
> Also, pg_class.relpages is an int. We don't have unsigned int columns.
Yeah. I had
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I did some research on this and generated the following patch. I didn't
> > find much in the way of problems except two vacuum.c fields that should
> > probably be BlockNumber. freespace.c also has a numPages field in
> > FSMRelatio
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I did some research on this and generated the following patch. I didn't
> find much in the way of problems except two vacuum.c fields that should
> probably be BlockNumber. freespace.c also has a numPages field in
> FSMRelation that is int. Should tha
We have the TODO item:
* Make sure all block numbers are unsigned to increase maximum table size
I did some research on this and generated the following patch. I didn't
find much in the way of problems except two vacuum.c fields that should
probably be BlockNumber. freespace.c also has a num
