Re: [PATCHES] [HACKERS] pg_buffercache causes assertion failure

2005-05-30 Thread Mark Kirkwood
Neil Conway wrote: On Tue, 2005-05-31 at 13:07 +1200, Mark Kirkwood wrote: I did some patches for 7.4 and 8.0 a while ago (attached) - while I do not expect these to be applied Right, I don't see a need to backport this. is there somewhere for things like this to go? Pg Foundry? Of

Re: [PATCHES] [HACKERS] pg_buffercache causes assertion failure

2005-05-30 Thread Neil Conway
On Tue, 2005-05-31 at 13:07 +1200, Mark Kirkwood wrote: > I did some patches for 7.4 and 8.0 a while ago (attached) - while I do > not expect these to be applied Right, I don't see a need to backport this. > is there somewhere for things like this to go? Pg Foundry? -Neil --

Re: [PATCHES] [HACKERS] pg_buffercache causes assertion failure

2005-05-30 Thread Mark Kirkwood
Tom Lane wrote: Mark Kirkwood <[EMAIL PROTECTED]> writes: This patch changes the use of numeric to int8 to represent the relblocknumber column. Applied, thanks. This reminds me: I did some patches for 7.4 and 8.0 a while ago (attached) - while I do not expect these to be applied (unles

Re: [PATCHES] [HACKERS] pg_buffercache causes assertion failure

2005-05-30 Thread Tom Lane
Mark Kirkwood <[EMAIL PROTECTED]> writes: > This patch changes the use of numeric to int8 to represent the > relblocknumber column. Applied, thanks. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists

Re: [PATCHES] [HACKERS] pg_buffercache causes assertion failure

2005-05-30 Thread Mark Kirkwood
Mark Kirkwood wrote: 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 shoul