Bug #38483 Federated storage engine NOT disabled as stated in release note

Submitted: 31 Jul 2008 10:47 Modified: 1 Aug 2008 16:36
Reporter: Bogdan Kecman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:5.0.64, 5.0.66a OS:Any
Assigned to: CPU Architecture:Any
Tags: build, federated

[31 Jul 2008 10:47] Bogdan Kecman
Description:
The release note for 5.0.64 states:

 The FEDERATED storage engine is now disabled by default
 in binary distributions. The engine is still available
 and can be enabled by starting the server with the
 --federated option. (Bug#37069)

Without any startup options, "SHOW ENGINES" returns "FEDERATED | YES",
and "show variables" returns "have_federated_engine | YES".

With "--skip-federated" option, they shows "DISABLED".

The binaries affected are (maybe some more):
5.0.64 and 5.0.66a for RHEL5 (x86, rpm)
5.0.66a for Windows (x86, with installer)

How to repeat:
install any of the affected binaries
execute 

SHOW ENGINES

Suggested fix:
disable the federated engine properly as stated in the release note
[31 Jul 2008 10:50] Daniel Fischer
In 5.0, federated is only disabled in the my.cnf files that we ship. In 5.1, the default of the server has changed to disable federated.
[1 Aug 2008 16:36] Paul DuBois
Noted in 5.0.64 changelog.

The FEDERATED storage engine is now disabled by default in the .cnf
files shipped with MySQL distributions (my-huge.cnf, my-medium.cnf,
and so forth). This affects server behavior only if you install one
of these files.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.044 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.