From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | vadim(at)krs(dot)ru (Vadim Mikheev) |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] 6.4.x |
Date: | 1998-12-01 23:15:52 |
Message-ID: | 199812012315.SAA06980@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tom Lane wrote:
> >
> > >>>> (3) does 6.4 support query lengths > 8192, or data blocks > 8192
> > >>>> (other than large objects)?
> >
> > > Sometime in the past Darren K. worked to parameterize this limit.
> >
> > There has been some discussion of allowing tuples to span multiple
> > disk blocks, which would remove the problem entirely, but it hasn't
> > happened yet. Maybe for 6.5?
>
> Right now I'm rewriting HeapTuple structure and functions - for
> multi-version concurrency control (MVCC). New HeapTuple:
>
> typedef struct HeapTupleData
> {
> uint32 t_len; /* length of *t_data */
> ItemPointerData t_self; /* SelfItemPointer */
> HeapTupleHeader t_data; /* */
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> this is what known as HeapTuple in < 6.5
> } HeapTupleData;
>
> I assume that one, who would like implement blocks spanning,
> will add something to this new structure.
> I need in ~ one week, please wait.
Block spanning was only an idea. No idea how to code it. Yet.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-12-01 23:27:41 | Re: [HACKERS] Re: Mysql 321 - Mysql 322 - msql |
Previous Message | The Hermit Hacker | 1998-12-01 21:01:11 | Re: [HACKERS] NT port |