; Yes, I'm to lazy to do it myself, what did you think :-p
> > >
> > >
> > > On Tue, Nov 30, 2010 at 4:01 PM, Wagner Bianchi <
> > wagnerbianch...@gmail.com
> > > > wrote:
> > >
> > >> Friends, I did a benchmark regarding to
gt; Friends, I did a benchmark regarding to this subject.
> >> Please, I am considering your comments.
> >> => http://wbianchi.wordpress.com/2010/11/30/insert-x-insert-delayed/
> >>
> >> Best regards.
> >> --
> >> WB
> >>
> >>
> >>
Yes, I'm to lazy to do it myself, what did you think :-p
>
>
> On Tue, Nov 30, 2010 at 4:01 PM, Wagner Bianchi > wrote:
>
>> Friends, I did a benchmark regarding to this subject.
>> Please, I am considering your comments.
>> => http://wbianchi.wordpre
Friends, I did a benchmark regarding to this subject.
> Please, I am considering your comments.
> => http://wbianchi.wordpress.com/2010/11/30/insert-x-insert-delayed/
>
> Best regards.
> --
> WB
>
>
> 2010/11/30 Wagner Bianchi
>
> Maybe, the table in use mus
Friends, I did a benchmark regarding to this subject.
Please, I am considering your comments.
=> http://wbianchi.wordpress.com/2010/11/30/insert-x-insert-delayed/
Best regards.
--
WB
2010/11/30 Wagner Bianchi
> Maybe, the table in use must be a table that is inside cache now - SHOW
tinguous table may well apply.
>
> No guarantees, though - I'm not that hot on this depth.
>
>
>
> On Tue, Nov 30, 2010 at 8:46 AM, WLGades wrote:
>
>> What I'm confused by though, is this line.
>>
>> "Note that INSERT DELAYED is slower than a
cked
against inserts", so the MyISAM insert-while-selecting at the end of a
continguous table may well apply.
No guarantees, though - I'm not that hot on this depth.
On Tue, Nov 30, 2010 at 8:46 AM, WLGades wrote:
> What I'm confused by though, is this line.
>
> "Note
What I'm confused by though, is this line.
"Note that INSERT DELAYED is slower than a normal INSERT if the table is not
otherwise in use." What's the definition of "in use"? Does a logging table
do that given that it's pretty much append-only/write-only?
Wayn
No, I think it's a good idea to do INSERT DELAYED here - it's only logging
application, and it's generally more important to not slow down the
application for that. It's only ever into a single table, so there's only
going to be a single delay thread for it anyway.
Archi
orts SELECT and INSERT. Maybe, a good deal to you, get rid
of you INSERT DELAYED:
- ALTER TABLE ENGINE = ARCHIVE;
Best regards.
--
WB
2010/11/29 WLGades
> I'm adding a table to our site that logs all page loads. In the past, when
> I built this, I used MyISAM and INSERT DELAYE
I'm adding a table to our site that logs all page loads. In the past, when
I built this, I used MyISAM and INSERT DELAYED. I went back to look at the
documentation to see if I should still do this, and saw this (taken from
http://dev.mysql.com/doc/refman/5.1/en/insert-delayed.html):
Note
> -Original Message-
> From: Dan Nelson [mailto:dnel...@allantgroup.com]
> Sent: Wednesday, September 29, 2010 2:26 PM
> To: Daevid Vincent
> Cc: 'MySQL'
> Subject: Re: INSERT DELAYED and created_on timestamps
>
> In the last episode (Sep 29), Daevi
In the last episode (Sep 29), Daevid Vincent said:
> I'm doing some reading on INSERT DELAYED
> http://dev.mysql.com/doc/refman/5.0/en/insert.html
>
> I have a user_log table:
>
> CREATE TABLE `user_log` (
> `id_user_log` bigint(20) unsigned NOT NULL auto_incre
I'm doing some reading on INSERT DELAYED
http://dev.mysql.com/doc/refman/5.0/en/insert.html
I have a user_log table:
CREATE TABLE `user_log` (
`id_user_log` bigint(20) unsigned NOT NULL auto_increment,
`id_user` int(10) unsigned default '0',
`created_on` timestamp N
lists,
I have tried utilizing partitioning (mysql 5.1.35 advanced version)
from mysql docs, it has been said that insert delayed on partitioning table
isn't supported.
and when perform insert like this:
insert delayed into tbla values(...);
the error that mentioned by documents is coming.
readers have the potential to cause your
insert queues to back up. INSERT DELAYED is a bandaid at best as it
just moves the problem around. It can still happen that delayed
inserts can timeout and never get writtien. Should the server be
interruputed you are in a posiution where your app thinks
operations to complete
read requests which arrive while a write is pending will wait until
the write is complete
Because of this, any slow readers have the potential to cause your
insert queues to back up. INSERT DELAYED is a bandaid at best as it
just moves the problem around. It can still
In the last episode (May 15), Dan Buettner said:
> Hi Edoardo -
>
> I think you've been misinformed; MyISAM tables do not support
> simultaneous read and write operations. MyISAM is a multiple
> reader/single writer, table locking design. You may want to switch
> to InnoDB tables for that f
omers)
CDRs are inserted directly from Asterisk switches when a call ends.
We're using INSERT DELAYED to store CDR because we don't want a report
query to get a lock on the CDR table and prevent CDRs from being
inserted immediatly (I need the query to return immediatly to avoid
strange int
We're using INSERT DELAYED to store CDR because we don't want a report
query to get a lock on the CDR table and prevent CDRs from being
inserted immediatly (I need the query to return immediatly to avoid
strange interacions with Asterisk)
1) I see that MyISAM tables should support INSERT a
>Description:
INSERT DELAYED crashes my new mysqld. Here is the error log:
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also
I also have the same problem upgrading from 4.1.15 to 5.0.15; this query
hang mysql:
INSERT DELAYED INTO phpads_adstats SET clicks = 0, views = 1, day =
NOW(), hour = HOUR(NOW()), bannerid = '97', zoneid = '15', source = ''
This is happening with every linux mys
ond.
Here is the SQL that crashes it:
INSERT DELAYED INTO views
SET ad_id='4',
host='pool-68-239-6-162.bos.east.verizon.net',
ip='1156515490'
Remove the DELAYED and no problems.
Here is a stack trace:
0x81876bc handle_segfault +
@t := now() |
+-+
| 2005-06-09 09:55:49 |
+-+
1 row in set (0.00 sec)
mysql> insert delayed into t set t = @t;
Query OK, 1 row affected (0.00 sec)
mysql> select * from t;
+-+
| t |
+-
Eric Bergen wrote:
How about something like this:
mysql> select @t := now();
+-+
| @t := now() |
+-+
| 2005-06-09 09:55:49 |
+-+
1 row in set (0.00 sec)
if the timestamp is not needed on the client with :
mysql> do @t := now(
1 row in set (0.00 sec)
> mysql> insert delayed into t set t = @t;
> Query OK, 1 row affected (0.00 sec)
> mysql> select * from t;
> +-+
> | t |
> +-+
> | 2005-06-09 09:55:49 |
> +-+
> 1 ro
How about something like this:
mysql> select @t := now();
+-+
| @t := now() |
+-+
| 2005-06-09 09:55:49 |
+-+
1 row in set (0.00 sec)
mysql> insert delayed into t set t = @t;
Query OK, 1 row affected (0.00 sec)
mysql&g
supposed to have a value that does not change
> >during a transaction. At which point during the transaction that value
> >is 'sampled' is implementation defined. (ISO/IEC 9075:2003-2 section
> >6.31)
> >
> >Since both NOW() and INSERT DELAYED are MySQL extensions
CURRENT_TIMESTAMP, which in MySQL is a
synonym for NOW(), is supposed to have a value that does not change
during a transaction. At which point during the transaction that value
is 'sampled' is implementation defined. (ISO/IEC 9075:2003-2 section
6.31)
Since both NOW() and INSERT DELAYED are MySQL ex
5:2003-2 section
6.31)
Since both NOW() and INSERT DELAYED are MySQL extensions I don't
particularly care how they behave/interfere, but I would prefer any
solution/hack not to complicate MySQL ever becomming standard
compliant in this regard (and standard compliance is an official
goal).
- Original Message -
From: "Jeff Smelser" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 09, 2005 7:50 AM
Subject: Re: INSERT DELAYED and NOW()
On Thursday 09 June 2005 09:39 am, Jeremiah Gowdy wrote:
I am proposing that when a query is received by MySQL, a timestamp
On Thursday 09 June 2005 09:39 am, Jeremiah Gowdy wrote:
> I am proposing that when a query is received by MySQL, a timestamp could be
> taken immediately, and that timestamp could travel with the query until it
> is actually processed. For delayed inserts, the query would still sit in
> the inse
I'm wondering if anyone else has run into this issue.
We are logging from a real-time telecom application (we have callers on the
phone that are being handled by threads that are logging to MySQL), and because
of the nature of that application, we use INSERT DELAYED. There are mul
Hi.
Send us information about operating sytem and MySQL version you use.
May be it will be helpful to install official binaries with enabled debug support of
the
latest release.
>I am using "INSERT DELAYED ..." to insert log records into a MyISAM table. Recently
>thes
I am using "INSERT DELAYED ..." to insert log records into a MyISAM table. Recently
these inserts have stopped showing up in the table, and extended-status shows them
coming in by increasing 'Delayed_writes', however 'Delayed_errors' is increasing by
the sam
"Insert Delayed" work on any version of MySql for INNODB tables?
The docs state that it does but I keep getting the error that the engine
> doesn't support this.
I did some investigation of this and here is the result:
What used to happen with "INSERT DELAYED" for InnoDB
Thanks for verifying that.
Dan
-Original Message-
From: John McCaskey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 13, 2004 12:23 PM
To: Daniel Cummings
Cc: [EMAIL PROTECTED]
Subject: Re: Insert Delayed
I verified the same error for myself, and then found:
http://bugs.mysql.com
Does "Insert Delayed" work on any version of MySql for INNODB tables?
The docs state that it does but I keep getting the error that the engine
doesn't support this.
TIA
Dan
ere were apparently some insert delayed queries that I
guess were queued for execution before the alter, and tried to execute after. Since I
did not remove any columns, and none of the char data that was being inserted was over
20 chars, I do not understand why the inserts failed...
I noticed the
I have a daemon which uses MySQL (INSERT INTO) to log. The problem is,
whenever I try to do anything with the log table that takes a long
time, it makes the daemon freeze until the table is free again.
I'm thinking of making the daemon use INSERT DELAYED instead, so that
it won't get bl
>Description:
On an unsuccessful INSERT DELAYED using mysql_query(), there is disagreement
between the two functions mysql_error() and mysql_errno(). Specifically,
mysql_errno() will return 0 (indicating no error), whereas mysql_error()
will return what really happened, e.g. "Ta
ed to work? Exmple:
>
> session 1 session 2
> --- --
> create table junk (value int);
> create table junk2 (value int);
> lock table junk read;
> insert into
ion 2
--- --
create table junk (value int);
create table junk2 (value int);
lock table junk read;
insert into junk2 values (1);
insert delayed into junk values (2);
insert delayed into junk select
On Tue, Apr 02, 2002 at 08:53:27AM -0600, Rick Emery wrote:
> What happened when you tried this experiment?
I just did the following:
In one client connection, issued 'lock tables outgoing write'.
Then in another client connection, tried to do an 'insert delayed'
What happened when you tried this experiment?
-Original Message-
From: Viraj Alankar [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 02, 2002 8:50 AM
To: [EMAIL PROTECTED]
Subject: insert delayed and timestamps
Hello,
When using 'insert delayed' syntax and there is a times
Hello,
When using 'insert delayed' syntax and there is a timestamp field in the table
but not specified in the insert query, which timestamp is actually used when
the record ends up in the destination table? In other words, will the
timestamp value be the actual timestamp that the
Hi,
I'm using INSERT DELAYED to insert about 120GB of data into mysql from mysqldumpped
data from remote server. After the weekend I've found such output from our perl script
(after was dumped let's say 60GB):
Just dumping Mthermoautotrophicum.orf
Just dumping Mthermoautotro
Hi,
A quite strange bug just occurs with MySQL 4.0 :
When I execute show processlist, I get :
mysql> show processlist;
+---+-+---+++--+
---+
--
Subject : Database
Hello all,
We have various routines which Insert in to tables. And in some cases there
are alot of rows involved, which understandably can take some time.
I just want to check that my understanding of the INSERT DELAYED option is
correct. When using DELAYED, are all rows
Is there any way to flush all insert delayed tables at once, with 1 command?
--
\\|//
(@ @)
---oOO---(_)---OOo
||
| Mike Baranski |
| Security Managment Consulting |
| http
On Thursday 01 March 2001 11:03, Artem Koutchine wrote:
> Sinisa, i thought i pointed out that mysql ALWAYS
> crashes on any single INSERT DELAY anytime,
> any database, under any conditions and during any
> weather. NO single INSERT DELAY can be executed
> successfully.
This looks like a bug in
On Fri, Apr 06, 2001 at 07:26:14PM +0300, Heikki Tuuri wrote:
> Hi!
>
> The MySQL manual says that INSERT DELAYED only works for MyISAM
> and ISAM tables, but the parser does not check that the table type
> is correct. We have to block this in the parser.
>
> If you use
Hi!
The MySQL manual says that INSERT DELAYED only works for MyISAM
and ISAM tables, but the parser does not check that the table type
is correct. We have to block this in the parser.
If you use it on Innobase tables, that can cause severe database
corruption!
Regards,
Heikki Tuuri
Innobase
Hi!
The MySQL manual says that INSERT DELAYED only works for MyISAM
and ISAM tables, but the parser does not check that the table type
is correct. We have to block this in the parser.
If you use it on Innobase tables, that can cause several database
corruption!
Regards,
Heikki Tuuri
Innobase
What happens if i use INSERT DELAYED and the client sends a lot of
messages, much more that mysql is able to handle?
(like when you log to a sql database, and you got lots of messages)
--
Florin Andrei
-
Before posting
I implemented a mysql based user tracker. On every visit
of a user I log some data to the DB.
Experimenting with INSERTs I used DELAYED and benchmarked
the page. An DELAYED insert takes aprox. 9 times more to
execute than an insert.
I am using PHP. When I call the query function it takes 9 time
ment that appears
> > to be similar. An advantage is that i know precisely what was taking place.
> > Consider the following:
> > 1) A servlet makes a single 'insert delayed' into a relation. (no auto increment
> > field - and just a simple primary key char(16) )
>
Steven,
I had an experience the other day in a controlled test environment that appears
to be similar. An advantage is that i know precisely what was taking place.
Consider the following:
1) A servlet makes a single 'insert delayed' into a relation. (no auto increment
field - and jus
Hi!
>>>>> "Lance" == Lance Lovette <[EMAIL PROTECTED]> writes:
Lance> If I INSERT DELAYED into a table with an auto_increment column and specify a
Lance> value of NULL for that column, the query fails. This is to be expected.
Lance> After this fail
Hi!
Does MySQL's insert delayed handler insert concurrently with selects on
MyISAM tables like the non-delayed inserts?
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
-
Before posting, please
I am confused about the way INSERT DELAYED reacts to setting an
auto_increment field to NULL. I am inserting records into a table where one
of the columns is auto_increment. Usually when setting the value of an
auto_increment field in an INSERT query I pass a value of NULL. When I do
the same
Lance Lovette writes:
> If I INSERT DELAYED into a table with an auto_increment column and specify a
> value of NULL for that column, the query fails. This is to be expected.
> After this failure however, normal INSERT queries start piling up in the
> 'Locked'
I forget to give the tail of the error log:
010307 12:33:41 Aborted connection 90714 to db: 'logging' user: 'apache'
host: `neo.f' (Got timeout reading communication pac
kets)
010307 12:33:41 Aborted connection 90722 to db: 'logging' user: 'apache'
host: `morpheus.f' (Got timeout reading commun
Hi,
I was trying to use debugging (creating a trace and log file) in order to
find the crashing problem we have been experiencing. However, I tend to come
up against another problem in the course of things -- mysql not shutting
down.
This time I have a log file and a trace file. When I shut down
If I INSERT DELAYED into a table with an auto_increment column and specify a
value of NULL for that column, the query fails. This is to be expected.
After this failure however, normal INSERT queries start piling up in the
'Locked' state and remain there indefinitely. The only way to
AIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 01, 2001 8:58 PM
Subject: Re: INSERT DELAYED still keeps CRUSHING (trying everything)
> Artem Koutchine writes:
> > Hello again!
> >
> > In the prev episode i said that whe
Artem Koutchine writes:
> Hello again!
>
> In the prev episode i said that when i do INSERT DELAYED
> mysql just catches sig 11, crashes and restarts. No record
> inserted whatsoever. Nothing is written into the update log.
>
> Here is a sample (even though it says
Hello again!
In the prev episode i said that when i do INSERT DELAYED
mysql just catches sig 11, crashes and restarts. No record
inserted whatsoever. Nothing is written into the update log.
Here is a sample (even though it says 1 row affected, it is
actually not affected. nothing is inserted
Hi!
I have posted a message about INSERT DELAYED
crashing the 3.23.33 server build from tar ball
on FreeBSD 4.2-STABLE using
--felide-constructors
--fno-exceptions
--fno-rtti
to make it work on high loads. However, with
or without mentioned compiler params i could never
do any INSERT DELAYED on
> create table test (
-> a1 tinyint unsigned not null,
-> a2 tinyint unsigned not null,
-> a3 tinyint unsigned not null,
-> a4 tinyint unsigned not null,
-> primary key (a1,a2,a3,a4)
-> );
->
-> So, to make it faster i want to use
faster i want to use INSERT DELAYED,
however, when i do so, i get a message "Server has gone away"
and the in the .err log i see mysqld got signal 11.
I could not use INSERT DELAY in 3.23.30 and up. never tried it
earlier.
Now other problems detected whatsoever under any amount
of load.
Hi all,
I was curious if anyone has been experiencing problems with INSERT DELAYED
lately. At the moment, it seems to limited to INSERT DELAYED and tables with
a FULLTEXT index. After a while, a lock on table prevents any normal INSERTS
or SELECTS (this behavior may require doing both normal and
) 1 41 66 77 88, Fax: +33 (0) 1 41 66 77 67
> -Original Message-
> From: Ord Millar [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 21, 2001 3:30 AM
> To: MySQL List (E-mail)
> Subject: Insert delayed & locks
>
>
> I had some trouble using insert delayed -
I had some trouble using insert delayed - I wonder if anyone can shed some
light on the problem.
I have a table for logs that records are inserted into regularly - once
every 10 seconds or so. I tried to update record in the table, but the
update just waited forever, it seemed to be waiting
74 matches
Mail list logo
