think it issues a segfault.
- Original Message -
From: "Micah Stevens" <[EMAIL PROTECTED]>
To: "JP Hindin" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, March 22, 2007 5:24 PM
Subject: Re: max_rows query + SegFaulting at inopportune times
Oh, I didn'
Oh, I didn't see the first comment. My mistake. It's likely a 32bit
integer size limit of some sort then. 32bit = 4gbytes
-Micah
On 03/22/2007 02:08 PM, JP Hindin wrote:
Micah;
In the first eMail I mentioned that I had excluded filesystem size limits
by manually producing a 14GB tar file. If
Micah;
In the first eMail I mentioned that I had excluded filesystem size limits
by manually producing a 14GB tar file. If it was only that simple :)
On Thu, 22 Mar 2007, Micah Stevens wrote:
> This table size is based on your filesystem limits. This is a limit of
> the OS, not MySQL.
>
> -Micah
This table size is based on your filesystem limits. This is a limit of
the OS, not MySQL.
-Micah
On 03/22/2007 01:02 PM, JP Hindin wrote:
Addendum;
On Thu, 22 Mar 2007, JP Hindin wrote:
Zero improvement. I used the following CREATE:
MAX_ROWS=10;
At first I thought I
I have, after further googling, discovered that the 4.2 billion figure
that MySQL uses as 'max_rows' is, indeed, max_rows and not a max database
size in bytes. In theory I have solved my problem, and wasted however many
peoples bandwidth by putting all these eMails to the MySQL list.
Mea culpa, m
Addendum;
On Thu, 22 Mar 2007, JP Hindin wrote:
> Zero improvement. I used the following CREATE:
> MAX_ROWS=10;
At first I thought I had spotted the obvious in the above - the MAX_ROWS I
used is smaller than the Max_data_length that resulted, presumably MySQL
being smarter than I a
ot;Michael Dykman" <[EMAIL PROTECTED]>
> Cc: "JP Hindin" <[EMAIL PROTECTED]>;
> Sent: Thursday, March 15, 2007 2:09 PM
> Subject: Re: max_rows query + SegFaulting at inopportune times
>
>
> >
> > On Thu, 15 Mar 2007, Michael Dykman wrote:
&g
PROTECTED]>
To: "Michael Dykman" <[EMAIL PROTECTED]>
Cc: "JP Hindin" <[EMAIL PROTECTED]>;
Sent: Thursday, March 15, 2007 2:09 PM
Subject: Re: max_rows query + SegFaulting at inopportune times
On Thu, 15 Mar 2007, Michael Dykman wrote:
What host OS are you
On Thu, 15 Mar 2007, Michael Dykman wrote:
> What host OS are you running? And which file system? MySQL is always
> limited by the file size that the host file system can handle.
"Deb Sarge" is a Linux distribution, the "large file support" I mentioned
allows files up to 2 TB in size.
> On 3/15/
What host OS are you running? And which file system? MySQL is always
limited by the file size that the host file system can handle.
- michael dykman
On 3/15/07, JP Hindin <[EMAIL PROTECTED]> wrote:
Greetings all;
I have a quandary regarding table limits, and clearly I am not
understanding ho
On 25 Feb 2004 at 8:35, Tucker, Gabriel wrote:
> What values of MAX_ROWS and AVG_ROW_LENGTH would I need so that I
> could limit this table to 3 [or n] number of records?
You can't. That's not what MAX_ROWS and AVG_ROW_LENGTH are for.
They're only there to allow MySQL to decide how many bytes
? How do I calculate this?
Additionally, is there a better way, not using the OS, to limit the size of MyISAM
tables?
Thanks
Gabe
-Original Message-
From: Keith C. Ivey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 24, 2004 5:11 PM
To: [EMAIL PROTECTED]
Subject: Re: MAX_ROWS
On 24 Feb
On 24 Feb 2004 at 22:01, Alison W wrote:
> Yes: MAX_ROWS is a *guidance* to the system in setting up the table
> and not a *limit* in any way.
Well, it is a limit in one way. MySQL uses it (in MyISAM tables) to
calculate the size of the pointer used for positions within the data
file. If the
> I wanted to test how the max_rows parameter works. I set it to 3 on a
> table. And, I was able to add 33 records [I stopped at this point]. It
> never prevented me from adding more records. The result is NOT what I
> expected. I expected that upon attempting to add the 4th record, I would
>
On Tue, 2002-06-18 at 11:43, Aborla.net - webmaster wrote:
> Hello,
>
> I created a table using:
> "CREATE TABLE a (pa VARCHAR (255) NOT NULL, pi VARCHAR (255), PRIMARY KEY
> (pa)) TYPE=HEAP MAX_ROWS=10"
>
> Then I inserted 16 recors. Later I done SELECT * FFROM a and mysql returned
> 16 records
15 matches
Mail list logo
