| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_buffercache causes assertion failure |
| Date: | 2005-05-30 21:53:20 |
| Message-ID: | 429B8B50.90500@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Mark Kirkwood wrote:
>
> I couldn't use int4 as the underlying datatype is unsigned int (not
> available as exposed Pg type). However, using int8 sounds promising (is
> int8 larger than unsigned int on 64-bit platforms?).
Blocknumber is defined as uint32 in block.h - so should always be safe
to represent as an int8 I am thinking.
I will look at patching pg_buffercache, changing numeric -> int8 for the
relblocknumber column. This seems a tidier solution than using numeric,
and loses the numeric overhead.
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2005-05-30 23:27:19 | Re: pg_buffercache causes assertion failure |
| Previous Message | Bruce Momjian | 2005-05-30 21:08:23 | Re: [HACKERS] Inherited constraints and search paths (was |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2005-05-30 23:27:19 | Re: pg_buffercache causes assertion failure |
| Previous Message | Gladys | 2005-05-30 21:35:40 | Platinum Stock Reports |