Berner,

First, I've corrected you e-mail so that it goes to the list, and not to
me directly.

> I use my PostgreSQL 8.0.4 as Catalogue-Database for Bacula.
> Bacula is a Backupsoftware.

Yes. The lead contributor to Bacula is a active PostgreSQL project
participant; I'll see if he'll look into your issue.

> When I backing up System (lot of very small Files) then PostgreSQL seams to by the bottleneck by inserting Catalogueinformation of every single File.
> The System on which Postgres runs is a Sun Solaris 10 Server on a Sun Fire V240 with 1GB RAM, 1CPU (SUNW,UltraSPARC-IIIi at 1.3GHz), 2 Ultra SCSI-3 Disks 73GB at 10k RPM which are in Raid1 (Solaris Softraid).
>
> Can someone gif me a hint for compiling PostgreSQL or configuring the Database.
>
> fsync is already disabled..

This is a bad idea if you care about your database.

So, PostgreSQL 8.1 is now official supported by Sun and ships with
Solaris 10 update 2 or later. It is recommended that you use that
rather and an out-of-date version. Second, see
www.powerpostgresql.com/PerfList

--Josh Berkus


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Hi...

Bacula does no transaction right now, so every insert is done separately with
autocommit.
Moreover, the insert loop for the main table is done by several individual
queries to insert data in several tables (filename, dir, then file), so this
is slow.
There's work underway to speed that up, using a big COPY to a temp table,
then queries to dispatch the records in the right places as fast as
possible. The patch has been made, but as it is a noticeable change in the
core, will take some time to be integrated... See the thread about that in
the bacula devel list a few weeks ago... Anyhow, our benchmark for now shows
a 10-20 times speedup with postgresql, fsync stays on, and it becomes faster
than mysql, and scales with the number of cpus... I cannot tell when/if it
will be included, but there's work on this.

For now, the only thing you can do is fsync=off, knowing you're taking a
chance with the data (but it's not that big a problem, as it's only bacula's
database, and can be rebuilt from the tapes or from a dump...) or a writeback
disk controller.



On Friday 17 November 2006 19:44, Josh Berkus wrote:
> Berner,
>
> First, I've corrected you e-mail so that it goes to the list, and not to
> me directly.
>
> > I use my PostgreSQL 8.0.4 as Catalogue-Database for Bacula.
> > Bacula is a Backupsoftware.
>
> Yes. The lead contributor to Bacula is a active PostgreSQL project
> participant; I'll see if he'll look into your issue.
>
> > When I backing up System (lot of very small Files) then PostgreSQL seams
> > to by the bottleneck by inserting Catalogueinformation of every single
> > File. The System on which Postgres runs is a Sun Solaris 10 Server on a
> > Sun Fire V240 with 1GB RAM, 1CPU (SUNW,UltraSPARC-IIIi at 1.3GHz), 2
> > Ultra SCSI-3 Disks 73GB at 10k RPM which are in Raid1 (Solaris Softraid).
> >
> > Can someone gif me a hint for compiling PostgreSQL or configuring the
> > Database.
> >
> > fsync is already disabled..
>
> This is a bad idea if you care about your database.
>
> So, PostgreSQL 8.1 is now official supported by Sun and ships with
> Solaris 10 update 2 or later. It is recommended that you use that
> rather and an out-of-date version. Second, see
> www.powerpostgresql.com/PerfList
>
> --Josh Berkus
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate