On Tue, Mar 31, 2015 at 10:27 PM, Marko Weber | 8000 we...@zbfmail.de
wrote:
hello list,
again i have to ask.
Do i need to run mysql_upgrade after upgrading mysql 5.5 5.6 ?
I ask because the post install text recommend this after an major upgrade.
On the Mysql Website is a major upgrade
On Tue, 31 Mar 2015 22:27:38 +0200, Marko Weber | 8000 wrote:
Do i need to run mysql_upgrade after upgrading mysql 5.5 5.6 ?
I ask because the post install text recommend this after an major
upgrade.
Do you *need* to? Possibly not. Should you do it? Yes.
If you run it unnecessarily, it
hello list,
again i have to ask.
Do i need to run mysql_upgrade after upgrading mysql 5.5 5.6 ?
I ask because the post install text recommend this after an major
upgrade.
On the Mysql Website is a major upgrade 5.5 6.0, not 5.5 5.6
So i ask you guys.
Any can help me?
thank you
marko
Hi list,
the dev-db/mysql will update from 5.5 to 5.6
At the end a post install text tells me i have to fire up mysql_upgrade
when this is a major update.
On the mysql site i found this
5.5.40
5.x.x is the major nr
x.5.x is the release nr
x.x.40 is the level of the release
so, do i have
Hi,
i have a server with dev-db/mysql-5.5.40 and dev-lang/php-5.3.29 .
After the upgrade from dev-db/mysql-5.5.40 to dev-db/mysql-5.6.22 the
mysql_connect give some warnings:
PHP Warning: mysql_connect(): Headers and client library minor version
mismatch. Headers:50540 Library:50622 in
On Tuesday 01 November 2005 04:58 pm, C. Beamer wrote:
A better description would have been that the restore worked. However,
the only database that was restored was the test database. The database
that I had created by creating a directory that was named after the
database that I had
Jeff Smelser wrote:
On Tuesday 01 November 2005 04:58 pm, C. Beamer wrote:
The database
that I had created by creating a directory that was named after the
database that I had created when using FC4 and then copying my database
related files into it, did not back up. Hence my assumption
C. Beamer wrote:
This works and is not a big deal. As I said, I'm just curious if there
is a way to fix things so that my database will be backed up properly
with the mysqldump process that is run when upgrading. As I also
stated, I haven't had the chance to try dumping the existing database
On Wednesday 02 November 2005 12:52 pm, C. Beamer wrote:
Up until now, what I needed to do in MySQL, I could do just fine and
never even knew about mysqldump until recently. As I previously stated,
I've only been using Gentoo since September. When I used to use FC4,
all I ever did was make
Jeff Smelser wrote:
Well, then you would be more interested in mysqlhotcopy.. That pretty much
does what your doing..
Mysql INC has yet to make a real backup/restore procedure for mysql. So
mysqldump or mysqlhotcopy is pretty much it. If you use innodb, I would go
after ibbackup. (not
On Wednesday 02 November 2005 02:23 pm, kashani wrote:
Because once you start caring about your db that much it's usually
easier to setup a crap box that replicates off your master. Then you can
lock the whole db on your slave and do a mysqldump without causing
issues on your main db
Jeff Smelser wrote:
On Wednesday 02 November 2005 02:23 pm, kashani wrote:
Because once you start caring about your db that much it's usually
easier to setup a crap box that replicates off your master. Then you can
lock the whole db on your slave and do a mysqldump without causing
Jeff Smelser wrote:
On Wednesday 02 November 2005 05:47 pm, kashani wrote:
So yes, if your db is 20 GB or less, what I mentioned will probably
work without too much trouble. If your db is 100 GB or larger, you're
likely spending enough on hardware and software to solve your issues
that
Hi,
Jeff Smelser wrote:
On Sunday 30 October 2005 05:15 pm, C. Beamer wrote:
The instructions on the Gentoo website for upgrading gave a step by step
to create a backup of my database. However, when I went to restore the
database after the upgrade, the restore didn't work. I'm thinking
Hi all,
I just upgraded MySQL using the instructions on the Gentoo website. For
the most part, everything went fine and now everything works, but I had
to make a couple of adjustments. My question now is if there is a
proper way to do what I did as a workaround.
In September, when I wiped
On 10/30/05, C. Beamer [EMAIL PROTECTED] wrote:
Hi all,
I just upgraded MySQL using the instructions on the Gentoo website. For
the most part, everything went fine and now everything works, but I had
to make a couple of adjustments. My question now is if there is a
proper way to do what I
Qian Qiao wrote:
The instructions on the Gentoo website for upgrading gave a step by step
to create a backup of my database. However, when I went to restore the
database after the upgrade, the restore didn't work. I'm thinking that
it was because of the way I got my database files into MySQL
On 10/30/05, C. Beamer [EMAIL PROTECTED] wrote:
Qian Qiao wrote:
What was the error message, if it was about the key length exceeding
1000, then you hit a known bug.
No, I didn't get any error messages on restoring the database that was
created by the backup process that was included in
Qian Qiao wrote:
On 10/30/05, C. Beamer [EMAIL PROTECTED] wrote:
Qian Qiao wrote:
What was the error message, if it was about the key length exceeding
1000, then you hit a known bug.
No, I didn't get any error messages on restoring the database that was
created by the backup
On 10/31/05, C. Beamer [EMAIL PROTECTED] wrote:
Qian Qiao wrote:
So the mysqldump you did on the 4.0 didn't dump the databases other
than test, hmmm.
That's correct. And as stated in my original post, I think it might
have something to do with the way I got the database into Gentoo -
20 matches
Mail list logo
