List:Bugs« Previous MessageNext Message »
From:Sinisa Milivojevic Date:April 23 2001 1:27pm
Subject:Re: 4 GB table size problem [NO BUG REPORT]
View as plain text  
Wolfgang Hurst writes:
> 
> Hi everybody,
> 
> we have a big problem. we using mysql 3.23.35.
> 
> our tables are very large and excced the 4 Gigabyte per table.
> 
> now, we split the table into mounthly stats tables, like Mar2001, Apr2001
> and so on.
> 
> my question is: have i a change to compile or switch some switch to allow
> more than 4 GB per table.
> 
> we use an intel system with freebse .
> 
> Wolfgang Hurst
> 
> Network and Systemengineer     Tiscali / Nacamar Germany
> Sun Certified Professional       Robert Bosch Strasse 32
> Phone: +49-6103-916-993           Germany 63303 Dreieich


Hi!


Hi!

To this mailing list we only accept full repeatable bug reports
as defined in the MySQL manual.

A complete bug report is done in the following manner:

1) First check the reference manual and the mail archive !
   We try very hard to keep the manual up to date so most questions
   can usually be solved by looking it up.

   Write in the mail that you have checked the reference manual and
   mail archive so others know that you have tried to solve the
   problem yourself.

2) ALWAYS use mysqlbug when posting questions about a MySQL version
   you are using!  mysqlbug is for bug reports AND questions.

3) Send the bug report to the right mailing list.
   (See http://www.mysql.com/documentation/lists.html). If you are unsure
   you should use mysql@stripped

4) Include a full example for the problem, including a full test case
   with all responses/error messages.

Thread
LAST_INSERT_ID returning wrong value after multiple row insert in a single queryLuc Van der Veken23 Apr
  • 4 GB table size problem [NO BUG REPORT]Wolfgang Hurst23 Apr
    • Re: 4 GB table size problem [NO BUG REPORT]Sinisa Milivojevic23 Apr
  • Re: LAST_INSERT_ID returning wrong value after multiple row insert in a single querySinisa Milivojevic23 Apr
  • LAST_INSERT_ID returning wrong value after multiple row insert in a single queryMichael Widenius23 Apr