There is something wrong with bugs.mysql.com email server I think.

I don't know if anyone from mysql is monitoring this list, but I think
there is something goofy going on with your email servers. I just now got
this email below. Uhm. I wrote that bug over a year and a half ago, and the
reply by Susanne was the day after. WTF?

....better late than never I suppose, but maybe you should look into your
mail server Q and see if there are more "stuck" emails?!

-----Original Message-----
From: Bug Database [mailto:do-not-reply@mysql.com]
Sent: Tuesday, July 27, 2010 12:43 PM
To: daevid@daevid.com
Subject: #42774 [Com]: mysqldump command line switch to ignore temporary
tables

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at
http://bugs.mysql.com/?id=42774&edit=2

Comment by: Bugs System
Reported by: Daevid Vincent
Category: Client
Severity: S4 (Feature request)
Status: Verified
Version: 5.0.51a
OS: Linux
OS Details: Ubuntu
Tags: IGNORE, temporary, mysqldump
Defect Class: D5 (Feature request)

[12 Feb 2009 12:53] Susanne Ebrecht

Many thanks for writing a bug report.

Changed category because mysqldump is CLI.

Verified as described.

The problem is related to general indexing.

------------------------------------------------------------ ------------

[11 Feb 2009 21:05] Daevid Vincent

Description:
We have a live database with tables that are over 500M rows. We cannot
take the server down to do a backup, or in this case to delete
temporary tables. However we use temporary tables constantly to take
offloads (in SQL format, create a temp database/tables, then normalize
and re-insert that offload data into our main database). This happens
every minute or so and is increasing as we expand.

We would like a way to ignore temp tables from mysqldump's command
line.

/*!40000 ALTER TABLE `offload_temp_1d071827a37c402d8294d4ee65d86e4d`
DISABLE KEYS */;
/*!40000 ALTER TABLE `offload_temp_1d071827a37c402d8294d4ee65d86e4d`
ENABLE KEYS */;
/*!40000 ALTER TABLE `offload_temp_55cd7b89c3def439a9727821717428ec`
DISABLE KEYS */;
/*!40000 ALTER TABLE `offload_temp_55cd7b89c3def439a9727821717428ec`
ENABLE KEYS */;

So as you can see, we end up with HUGE amounts of temporary tables
being backed up and then on occasion re-imported. Then we don't know
which temp tables are stale vs. active (the active ones do remove
themselves, but our naming convention doesn't have dates)


How to repeat:
mysqldump --opts to dump out our entire database.

Suggested fix:
mysqldump --ignore-temp-tables

------------------------------------------------------------ ------------


--
http://bugs.mysql.com/42774


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

RE: There is something wrong with bugs.mysql.com email server I think (another one)

And now I just got yet another email for a different bug from 2008!! What's
going on here?

BTW, this bug is super annoying! How sad that in FOUR YEARS AND FOURTEEN
DAYS it is yet to be fixed. Seriously? This can't be that hard to fix, in
fact, it seems that Innodb would have to go out of it's way to be different
than the standard SQL logic.

> -----Original Message-----
> From: Daevid Vincent [mailto:daevid@daevid.com]
> Sent: Monday, August 02, 2010 12:35 PM
> To: 'MySQL List'
> Subject: There is something wrong with bugs.mysql.com email
> server I think.
>
> I don't know if anyone from mysql is monitoring this list, but I think
> there is something goofy going on with your email servers. I
> just now got
> this email below. Uhm. I wrote that bug over a year and a
> half ago, and the
> reply by Susanne was the day after. WTF?
>
> ...better late than never I suppose, but maybe you should
> look into your
> mail server Q and see if there are more "stuck" emails?!



-----Original Message-----
From: Bug Database [mailto:do-not-reply@mysql.com]
Sent: Sunday, August 01, 2010 4:04 AM
To: daevid@daevid.com
Subject: #21641 [Ver]: nonpreserving of InnoDB auto_increment values can
lead to unintended inheritance

Unsubscribe from updates to this bug at: http://bugs.mysql.com/21641

Updated by: Shane Bester
Reported by: Stephen Dewey
Category: Server: InnoDB
Severity: S4 (Feature request)
Status: Verified
-Version: 4.1.20
+Version: 4.1, 5.1, 5.5
-OS: Linux
+OS: Any
-OS Details: Linux (Red Hat)
+OS Details:
Tags: auto_increment, innodb
Defect Class: D5 (Feature request)

[20 Oct 2008 23:40] Mattias Jonsson

Closed bug#34077 as a duplicate of this.

------------------------------------------------------------ ------------

[13 Feb 2008 23:29] Dave Latham

The current functionality is definitely not intuitive. A persistent
auto-increment would be much appreciated!

------------------------------------------------------------ ------------

[19 Dec 2007 22:59] Mike Schumacher

I agree that this is a critical problem that needs to be addressed. We
are having all kinds of issues related to it. What is the status of
this bug?

------------------------------------------------------------ ------------

[4 Jun 2007 22:06] Dimitriy Alekseyev

What's the status of this feature request?

------------------------------------------------------------ ------------

[8 May 2007 3:20] Daevid Vincent

This bug is critical and is causing us all kinds of grief with database
integrity. Please escalate it.

mysqladmin create INNODB_IS_BROKEN

locutus ~ # mysql INNODB_IS_BROKEN
mysql> CREATE TABLE `foo` (
-> `id` int(10) unsigned NOT NULL auto_increment,
-> `name` varchar(20),
-> PRIMARY KEY (`id`)
-> ) ENGINE=INNODB;
Query OK, 0 rows affected (0.01 sec)

mysql> INSERT INTO foo values (null, 'a');
mysql> INSERT INTO foo values (null, 'b');
mysql> INSERT INTO foo values (null, 'c');

mysql> SELECT * FROM foo;
+----+------+
| id | name |
+----+------+
| 1 | a |
| 2 | b |
| 3 | c |
+----+------+
3 rows in set (0.00 sec)

mysql> DELETE FROM foo;
Query OK, 3 rows affected (0.00 sec)

mysql> QUIT;

locutus ~ # /etc/init.d/mysql restart
* Stopping mysql ...
* Starting mysql (/etc/mysql/my.cnf)

locutus ~ # mysql INNODB_IS_BROKEN
mysql> INSERT INTO foo values (null, 'd');
Query OK, 1 row affected (0.01 sec)

mysql> SELECT * FROM foo;
+----+------+
| id | name |
+----+------+
| 1 | d |
+----+------+
1 row in set (0.00 sec)

------------------------------------------------------------ ------------

[28 Aug 2006 13:08] Valeriy Kravchuk

Thank you for a reasonable feature request.

------------------------------------------------------------ ------------

Earlier comments can be viewed at http://bugs.mysql.com/21641


--
http://bugs.mysql.com/21641


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: There is something wrong with bugs.mysql.com email server I think(another one)

On 8/2/2010 3:39 PM, Daevid Vincent wrote:
> And now I just got yet another email for a different bug from 2008!! What's
> going on here?
>
> BTW, this bug is super annoying! How sad that in FOUR YEARS AND FOURTEEN
> DAYS it is yet to be fixed. Seriously? This can't be that hard to fix, in
> fact, it seems that Innodb would have to go out of it's way to be different
> than the standard SQL logic.

The messages you received are status change notifications to the bugs to
which you are subscribed. While I cannot get into any details about
why these bugs have been "working" for such a long time you should be
encouraged that they are under review, again.

--
Shawn Green
MySQL Principal Technical Support Engineer
Oracle USA, Inc.
Office: Blountville, TN

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: There is something wrong with bugs.mysql.com email server I think

Shawn,

On Mon, Aug 2, 2010 at 4:42 PM, Shawn Green (MySQL)
wrote:
> On 8/2/2010 3:39 PM, Daevid Vincent wrote:
>>
>> And now I just got yet another email for a different bug from 2008!!
>> What's
>> going on here?
>> BTW, this bug is super annoying! How sad that in FOUR YEARS AND FOURTEEN
>> DAYS it is yet to be fixed. Seriously? This can't be that hard to fix, i=
n
>> fact, it seems that Innodb would have to go out of it's way to be
>> different
>> than the standard SQL logic.
>
> The messages you received are status change notifications to the bugs to
> which you are subscribed. =A0While I cannot get into any details =A0about=
why
> these bugs have been "working" for such a long time you should be encoura=
ged
> that they are under review, again.

I have complained to a couple of MySQL'ers before about mystifying
emails that apparently show no change to the bug at all. I was told
that these are being sent when developers post private comments to the
bugs. I consider this a bug in the bug tracking system :-)

Baron

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: There is something wrong with bugs.mysql.com email server I think

On Sat, Aug 7, 2010 at 11:47 AM, Baron Schwartz wrote:
> I consider this a bug in the bug tracking system :-)

Severity: S4 (Feature request)


--
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org