On 6 Sep 2007 at 23:25, Kern Sibbald wrote: > On Thursday 06 September 2007 22:37, Scott Barninger wrote: > > On Thu, 2007-09-06 at 16:21 -0400, Dan Langille wrote: > > > On 6 Sep 2007 at 15:48, Scott Barninger wrote: > > > > On Thu, 2007-09-06 at 21:10 +0200, Kern Sibbald wrote: > > > > > On Thursday 06 September 2007 20:20, Dan Langille wrote: > > > > > > On 6 Sep 2007 at 20:16, Kern Sibbald wrote: > > > > > > > On Thursday 06 September 2007 19:38, Dan Langille wrote: > > > > > > > > The latest versions of Bacula (>= 2.2.0, I think) require a > > > > > > > > newer version of MySQL. We are now using nested selects, which > > > > > > > > older versions of MySQL do not have. I think the minimum > > > > > > > > requirement is MySQL 4.1 > > > > > > > > > > > > > > > > This is the second instances of this problem that I have > > > > > > > > noticed. > > > > > > > > > > > > > > > > Things we should do: > > > > > > > > > > > > > > > > 1 - Put out an announcement notifying people of this > > > > > > > > requirement. 2 - Update ReleaseNotes > > > > > > > > > > > > > > > > Things we could also do: > > > > > > > > > > > > > > > > 3 - Put checks in bacula-dir to check for database version >= > > > > > > > > that required. > > > > > > > > > > > > > > > > > > > > > > > > I can do #2 right away. > > > > > > > > > > > > I'll be doing that on the Branch-2.2... right? > > > > > > > > > > I think it is better to do it on the trunk where we can test it > > > > > before releasing. When it is well tested, either we will release the > > > > > trunk or we can merge it back into the Branch. I'm planning on > > > > > making a release of 3.0.0 very soon. > > > > > > > > > > > > I assume you mean check for MySQL version. The term database > > > > > > > version usually refers to Bacula's internal table format. > > > > > > > > > > > > Yes. > > > > > > > > > > > > > > Kern: can you do #1? > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > > #3 would be a nice to have, and would help reduce the number of > > > > > > > > support calls. I don't think it's a big priority. > > > > > > > > > > > > > > Can you tell me where the nested selects are, and are you sure > > > > > > > that MySQL 4.1 is the first version that supports them? > > > > > > > > > > > > No, I'm not sure where they are, but the queries below will help > > > > > > locate them. > > > > > > > > > > From seeing the failed insert below, I would guess it is in the batch > > > > > insert code, so another thing you might want to try for older MySQL > > > > > versions is to build Bacula with batch insert disabled. > > > > > > > > Sounds like the rpm spec needs to have an additional configure option > > > > for 3.23.x? > > > > > > The original poster indicates he tried with batch insert turned off. > > > He still had problems. > > > > Yeah, I saw that after posting this. Question is, should I withdraw the > > 2.2.1 EL3 mysql package from sourceforge? And long term, do I need to > > stop support for EL3 since it also had the postgresql problem? > > Can you remind me what the PostgreSQL problem is?
I think Scott refers to our upcoming use of PQescapeStringCon() which is available only in PostgreSQL > 7.4 > I think it is a very bad thing to move Bacula forward so fast that we > start dropping somewhat older systems. So, I would really like to see > the details of what is going wrong and try to come up with some work > arounds. -- Dan Langille - http://www.langille.org/ Available for hire: http://www.freebsddiary.org/dan_langille.php ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
