Comment 4 for bug 584299

Revision history for this message
Peter Zaitsev (pz-percona) wrote : Re: [Bug 584299] Re: --innodb_doublewrite_path should accept absolute location

I do not understand you. Why you can't specify double write buffer location
same as you specify location for logs ?
What it has to do with ignoring innodb_data_file_path ?

On Mon, May 24, 2010 at 9:15 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> Peter,
>
> Ignoring innodb_data_home_dir is different behavior from original parameter
> "innodb_data_file_path".
> (Even it can be set relative from "datadir", doublewrite buffer is
> datafile)
>
> How to make explicit by its name...
> Do you have any idea about naming to explicit ignoring
> "innodb_data_file_path"?
>
> --
> --innodb_doublewrite_path should accept absolute location
> https://bugs.launchpad.net/bugs/584299
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona Server.
>
> Status in Percona Server with XtraDB: Triaged
>
> Bug description:
> Currently --innodb_doublewrite_path can be set only relatively to
> --innodb_data_home_dir, but it restricts usability.
> I want to be able to set it to any location.
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
http://www.percona.com/training/