> >Jose,
> >
> >I had some work done on this back in November, so I took some
> time to clean
> >it up, finished off some more and tested a patch.  I hope no one else has
> >invested much time in these pgsql bugs yet, but I believe this will close
> >both this one and 272191.
> >
> Well, i have received some patches during the last week, and i'm
> currently integrating them.

Ah, ok I rewrote most of the .postinst and .config files, and didn't see
activity in the bug system so you've got a fairly large patch there that
fixes everything I've found myself, & applies to 1.36.1-1.

You'll see it using 'su' to execute commands as the pg admin on a local
debian postgres install, to satisfy the default 'IDENT sameuser'
authentication.

> >At last you'll end up with a working bacula install with pgsql.
> >
> >
> Not me, but *we*. Thank you very much, again!
> Expect a Bacula-1.36.2 upload sometime early next week.

great!

I've got a second "optimization" patch that's specifically for postgres
users, gives a big speedup on backups.  Has no effect really if you use the
default "Multiple Connections = no" setting, but for a threadsafe db driver
like PG (and the patch will only affect PG currently) you can safely use
this patch and enable multiple connections, and get a big speedup which puts
PG almost on par with Mysql as far as backup timings.  Typically PG backups
are very slow, this patch puts multiple statements in one command, and cuts
overhead of mutexes when they aren't needed by a threadsafe driver when
transactions are enabled (the latter helps out on sub 3Ghz servers).

I've run this patch on our backup system in house, with millions of files, a
dozen clients, for 4 months with no trouble.  Again the default "multiple
connections" is off, so none of the above is enabled by default.

Let me know if you'd be interested in this patch to experiment with in the
debian package, possibly in the unstable tree.  I see a big advantage for
those wanting to use PG.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to