Hi Karl,
Having finally beaten the existing problem into submission and set up
triggers, monitors etc to check for new cases...
How would the iietabs accumulate? I'm looking at the iiextended_relation
catalog and its keyed on the etab_base. So I'm assuming here that if the
max number of pages was breached that I would see a new iietab created
to hold the spill, and a new entry in iiextended_relation with the same
etab_base, etab_attid but a different etab_extension. Yes?
BTW. What is etab_type for?
I'm currently trying to build a testcase for this. And am loading
8388600 rows into a simple table with a blob column. I can then add
extra row - which will cause an extra page to be loaded onto the iietab
and see what happens as we break the magic 8388608 mark.
I'll play with partitioned tables afterwards.
Marty
-----Original Message-----
From: info-ingres-bounces@[EMAIL PROTECTED]
On Behalf Of Karl
& Betty Schendel
Sent: 07 May 2008 15:31
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] page_size on iietabs
On May 7, 2008, at 9:51 AM, Martin Bowes wrote:
> BTW. Expanding to 8k will probably buy me another year before I'm
> in this problem again ... on this column. Can I make the etab a
> partitioned table?
>
>
>
No.
But etabs are supposed to accumulate if one fills up. Obviously that
is not
working, which would be a bug.
Also, I think I recall discovering that etabs on a partitioned base
table aren't quite right -- each partition gets its own etab, but
all the blob data goes into the partitioned master's etab, which
certainly wasn't what I had in mind originally. It's been
a while since I poked around with blobs in a partitioned
table, though.
You might want to go to 16K pages, or larger, instead of 8.
Karl
_______________________________________________
Info-Ingres mailing list
Info-Ingres@[EMAIL PROTECTED]
|
