We specify one file right ? In this case call it innodb_doublewrite_file
On Mon, May 24, 2010 at 11:32 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:
> OK.
>
> I will change to "innodb_doublewrite_home_dir". (filename is always
> ib_doublewrite)
> (like innodb_log_group_home_dir)
>
> Then it is natural usage as impression from the name, isn't it?
>
> --
> --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
Yasufumi,
We specify one file right ? In this case call it innodb_ doublewrite_ file
On Mon, May 24, 2010 at 11:32 PM, Yasufumi Kinoshita <
<email address hidden>> wrote:
> OK. doublewrite_ home_dir" . (filename is always log_group_ home_dir) doublewrite_ path should accept absolute location /bugs.launchpad .net/bugs/ 584299 doublewrite_ path can be set only relatively to data_home_ dir, but it restricts usability.
>
> I will change to "innodb_
> ib_doublewrite)
> (like innodb_
>
> Then it is natural usage as impression from the name, isn't it?
>
> --
> --innodb_
> https:/
> 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_
> --innodb_
> 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 www.percona. com/training/
http://