Debian Bug report logs - #591293
bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Thomas Arendsen Hein <thomas@intevation.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Sun, 01 Aug 2010 22:28:42 +0200

Package: bacula-director-pgsql
Version: 5.0.2-1~bpo50+1
Severity: normal


Hi!

This bug describes the identical problem as #584791 does, but since that bug
was closed due to lack of response from the original submitter and I don't
know how (if) reportbug can reopen a bug I submit this new one.
(and I guess mentioning backports in the subject is good, too)

I just tried to upgrade the bacula installation on a lenny machine from 2.4.4
to lenny-backports (currently the same version as in squeeze: 5.0.2).

During the automatic database upgrade I got the following message:

| An error seems to have occurred while upgrading the database. If it's of any help, this was the error encountered:
|
| NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "pathhierarchy_pkey" for table "pathhierarchy" NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "pathvisibility_pkey" for
| table "pathvisibility" ERROR: relation "file_jpfid_idx" already exists
|
| Fortunately, there should be a backup of the database made just before the upgrade in /var/cache/dbconfig-common/backups/bacula-director-pgsql_2.4.4-1.pgsql.
|
| At this point, you have the option to retry or abort the operation. If you choose "retry", you will be prompted with all the configuration questions once more and another attempt will be made at
| performing the operation. "retry (skip questions)" will immediately attempt the operation again, skipping all questions.  If you choose "abort", the operation will fail and you will need to downgrade,
| reinstall, reconfigure this package, or otherwise manually intervene to continue using it.
|
| Error upgrading database for bacula-director-pgsql.  Retry?
|
|                                                                                           abort
|                                                                                           retry
|                                                                                           retry (skip questions)
|
|
|                                                                                                   <Ok>

Above is the dialog output, with scrolling back the terminal I see the first
dialog where I was asked:

| Perform upgrade on database for bacula-director-pgsql with dbconfig-common?
(which I answered with "Yes")

Between the two dialogs is the the script output:

creating database backup in /var/cache/dbconfig-common/backups/bacula-director-pgsql_2.4.4-1.pgsql.
applying upgrade sql for 2.4.4-1 -> 3.0.0.
applying upgrade sql for 2.4.4-1 -> 5.0.0.
error encountered processing /usr/share/dbconfig-common/data/bacula-director-pgsql/upgrade/pgsql/5.0.0:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "pathhierarchy_pkey" for table "pathhierarchy" NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "pathvisibility_pkey" for table "pathvisibility" ERROR: relation "file_jpfid_idx" already exists


On this machine I can live with not running bacula backups for some time, so
it is available for further analysis.


BTW, the directory /var/cache/dbconfig-common/backups and the contained file
bacula-director-pgsql_2.4.4-1.pgsql are world readable. Against which package
should this be reported?

Regards,
Thomas

-- System Information:
Debian Release: 5.0.5
  APT prefers stable
  APT policy: (550, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bacula-director-pgsql depends on:
ii  bacula-common           5.0.2-1~bpo50+1  network backup, recovery and verif
pn  bacula-common-pgsql     <none>           (no description available)
pn  bacula-director-common  <none>           (no description available)
ii  dbconfig-common         1.8.39           common framework for packaging dat
ii  debconf [debconf-2.0]   1.5.24           Debian configuration management sy
ii  libc6                   2.7-18lenny4     GNU C Library: Shared libraries
ii  libgcc1                 1:4.3.2-1.1      GCC support library
ii  libpq5                  8.3.11-0lenny1   PostgreSQL C client library
ii  libssl0.9.8             0.9.8g-15+lenny7 SSL shared libraries
ii  libstdc++6              4.3.2-1.1        The GNU Standard C++ Library v3
ii  libwrap0                7.6.q-16         Wietse Venema's TCP wrappers libra
ii  postgresql-client       8.3.11-0lenny1   front-end programs for PostgreSQL 
ii  postgresql-client-8.3 [ 8.3.11-0lenny1   front-end programs for PostgreSQL 
ii  python2.5               2.5.2-15+lenny1  An interactive high-level object-o

Versions of packages bacula-director-pgsql recommends:
ii  postgresql-8.3            8.3.11-0lenny1 object-relational SQL database, ve

Versions of packages bacula-director-pgsql suggests:
pn  postgresql-contrib            <none>     (no description available)
pn  postgresql-doc                <none>     (no description available)

-- debconf information:
  bacula-director-pgsql/pgsql/authmethod-admin: ident
  bacula-director-pgsql/pgsql/no-empty-passwords:
  bacula-director-pgsql/upgrade-backup: true
  bacula-director-pgsql/install-error: abort
  bacula-director-pgsql/purge: false
  bacula-director-pgsql/pgsql/method: unix socket
  bacula-director-pgsql/db/app-user: bacula
  bacula-director-pgsql/dbconfig-reinstall: false
  bacula-director-pgsql/db/dbname: bacula
  bacula-director-pgsql/remote/host:
  bacula-director-pgsql/pgsql/admin-user: postgres
  bacula-director-pgsql/internal/skip-preseed: false
  bacula-director-pgsql/database-type: pgsql
  bacula-director-pgsql/remote/port:
  bacula-director-pgsql/remote/newhost:
  bacula-director-pgsql/remove-error: abort
  bacula-director-pgsql/passwords-do-not-match:
  bacula-director-pgsql/internal/reconfiguring: false
  bacula-director-pgsql/pgsql/authmethod-user: ident
  bacula-director-pgsql/pgsql/manualconf:
* bacula-director-pgsql/dbconfig-install: true
  bacula-director-pgsql/dbconfig-upgrade: true
  bacula-director-pgsql/missing-db-package-error: abort
  bacula-director-pgsql/dbconfig-remove:
  bacula-director-pgsql/upgrade-error: abort
  bacula-director-pgsql/pgsql/changeconf: false

Message #10 received at 591293@bugs.debian.org (full text, mbox, reply):

From: Thomas Arendsen Hein <thomas@intevation.de>

To: 591293@bugs.debian.org

Subject: Re: Bug#591293: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Thu, 19 Aug 2010 12:40:21 +0200

* Thomas Arendsen Hein <thomas@intevation.de> [20100801 22:30]:
> On this machine I can live with not running bacula backups for some time, so
> it is available for further analysis.

I just wanted to mention that the machine is still available for
further analysis.

Regards,
Thomas

-- 
thomas@intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Message #15 received at 591293@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: Thomas Arendsen Hein <thomas@intevation.de>, 591293@bugs.debian.org

Subject: Re: Bug#591293: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Thu, 19 Aug 2010 15:33:44 -0500

On 08/19/2010 05:40 AM, Thomas Arendsen Hein wrote:
> * Thomas Arendsen Hein<thomas@intevation.de>  [20100801 22:30]:
>> On this machine I can live with not running bacula backups for some time, so
>> it is available for further analysis.
>
> I just wanted to mention that the machine is still available for
> further analysis.

Thank you for the reminder.  I was out of town when this was reported.

Can you look at your dpkg.log and get the precise version that was 
installed prior to the upgrade?  Also, is it possible to gzip that 
backup and attach it to the bug?  (I would note that it may contain 
filenames and other data from your machine, so think carefully before 
answering yes because this will be public.  It will not contain 
*contents* of files.)

Message #20 received at 591293@bugs.debian.org (full text, mbox, reply):

From: Thomas Arendsen Hein <thomas@intevation.de>

To: John Goerzen <jgoerzen@complete.org>

Cc: 591293@bugs.debian.org

Subject: Re: Bug#591293: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Fri, 20 Aug 2010 20:53:54 +0200

* John Goerzen <jgoerzen@complete.org> [20100819 22:49]:
> On 08/19/2010 05:40 AM, Thomas Arendsen Hein wrote:
>> * Thomas Arendsen Hein<thomas@intevation.de>  [20100801 22:30]:
>>> On this machine I can live with not running bacula backups for some time, so
>>> it is available for further analysis.
>>
>> I just wanted to mention that the machine is still available for
>> further analysis.
>
> Thank you for the reminder.  I was out of town when this was reported.

That's what I guessed :)

> Can you look at your dpkg.log and get the precise version that was  
> installed prior to the upgrade?

2010-08-01 21:58:55 upgrade bacula-director-pgsql 2.4.4-1 5.0.2-1~bpo50+1

The history before that was that I used bacula-director-sqlite3
2.2.8-8 in the past and switched to postgresql without
importing/converting the old catalog when bacula 2.4.2-3.1 was the
current version in lenny/testing. dbconfig-common is still at
1.8.39:

16.11.2008      thomas
* apt-get install --purge bacula-director-pgsql bacula-sd-pgsql:
  Purg bacula-director-sqlite3 [2.4.2-3.1] [bacula-server ]
  Purg bacula-sd-sqlite3 [2.4.2-3.1] [bacula-server ]
  Inst dbconfig-common (1.8.39 Debian:testing) [bacula-server ]
  Inst postgresql-client-common (91 Debian:testing) [bacula-server ]
  Inst postgresql-client-8.3 (8.3.5-1 Debian:testing) [bacula-server ]
  Inst postgresql-client (8.3.5-1 Debian:testing) [bacula-server ]
  Inst bacula-director-pgsql (2.4.2-3.1 Debian:testing) [bacula-server ]
  Inst bacula-sd-pgsql (2.4.2-3.1 Debian:testing)
  Inst postgresql-common (91 Debian:testing)
  Inst postgresql-8.3 (8.3.5-1 Debian:testing)

28.12.2008      thomas
* apt-get upgrade:
  Inst bacula-console-qt [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-fd [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-console [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-console-wx [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-sd-pgsql [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-traymonitor [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-director-pgsql [2.4.2-3.1] (2.4.3-1 Debian:testing) []
  Inst bacula-common [2.4.2-3.1] (2.4.3-1 Debian:testing) [bacula-sd on bacula-common] [bacula-director-
common on bacula-common] [bacula-sd bacula-director-common ]
  Inst bacula-director-common [2.4.2-3.1] (2.4.3-1 Debian:testing) [bacula-sd on bacula-common] [bacula-
sd ]
  Inst bacula-sd [2.4.2-3.1] (2.4.3-1 Debian:testing)
  Inst bacula-server [2.4.2-3.1] (2.4.3-1 Debian:testing)

23.01.2009      thomas
* apt-get upgrade:
  Inst bacula-console-qt [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-fd [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-console [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-console-wx [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-sd-pgsql [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-traymonitor [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-director-pgsql [2.4.3-1] (2.4.4-1 Debian:testing) []
  Inst bacula-common [2.4.3-1] (2.4.4-1 Debian:testing) [bacula-sd on bacula-common] [bacula-director-co
mmon on bacula-common] [bacula-sd bacula-director-common ]
  Inst bacula-director-common [2.4.3-1] (2.4.4-1 Debian:testing) [bacula-sd on bacula-common] [bacula-sd
 ]
  Inst bacula-sd [2.4.3-1] (2.4.4-1 Debian:testing)
  Inst bacula-doc [2.4.1-1] (2.4.4-1 Debian:testing)
  Inst bacula-server [2.4.3-1] (2.4.4-1 Debian:testing)

01.08.2010      thomas
* apt-get install -t lenny-backports --auto-remove --purge bacula bacula-client bacula-server:
  Inst bacula-traymonitor [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) []
  Inst bacula-common-pgsql (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) []
  Inst bacula-fd [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) []
  Inst bacula-director-pgsql [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) []
  Inst bacula-common [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) [bacula-sd o
n bacula-common] [bacula-director-common on bacula-common] [bacula-console bacula-sd bacula-director-com
mon bacula-console-qt ]
  Inst bacula-director-common [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) [ba
cula-sd on bacula-common] [bacula-console bacula-sd bacula-console-qt ]
  Inst bacula-console [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) [bacula-sd 
on bacula-common] [bacula-sd bacula-console-qt ]
  Inst bacula-console-qt [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) [bacula-
sd on bacula-common] [bacula-sd ]
  Inst bacula-sd [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports) [bacula-sd-pgsql
 ]
  Inst bacula-sd-pgsql [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports)
  Purg libqwt5-qt4 [5.1.1-1]
  Inst bacula-server [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports)
  Inst bacula-client [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports)
  Inst bacula [2.4.4-1] (5.0.2-1~bpo50+1 Backports.org archive:None/lenny-backports)


> Also, is it possible to gzip that  
> backup and attach it to the bug?  (I would note that it may contain  
> filenames and other data from your machine, so think carefully before  
> answering yes because this will be public.  It will not contain  
> *contents* of files.)

With gzip it is still 119MB, so probably too big to attach it.
Besides that the file names contain too much personal data, e.g.
names of people.

Regards,
Thomas

-- 
thomas@intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Message #25 received at 591293@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: Thomas Arendsen Hein <thomas@intevation.de>

Cc: 591293@bugs.debian.org

Subject: Re: Bug#591293: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Fri, 20 Aug 2010 14:41:42 -0500

On 08/20/2010 01:53 PM, Thomas Arendsen Hein wrote:
>
> 2010-08-01 21:58:55 upgrade bacula-director-pgsql 2.4.4-1 5.0.2-1~bpo50+1
>
> The history before that was that I used bacula-director-sqlite3
> 2.2.8-8 in the past and switched to postgresql without
> importing/converting the old catalog when bacula 2.4.2-3.1 was the
> current version in lenny/testing. dbconfig-common is still at
> 1.8.39:

OK, let me restate that and make sure I understand correctly.

1. You used to use bacula-director-sqlite3 version 2.2.8-8.

2. At some point you installed bacula-director-pgsql 2.4.2-3.1 instead.

3. You started with a freshly-installed new catalog when you installed 
2.4.2-3.1, and made no effort to migrate the old catalog to it.

4. You made no changes to the database schema manually at any point.

5. You upgraded to 2.4.4-1 over time.

6. Then you had an error when upgrading from 2.4.4 to 5.0.2.

Is that correct?

-- John

Message #30 received at 591293@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: 591293@bugs.debian.org, control@bugs.debian.org

Subject: Diagnosis

Date: Fri, 20 Aug 2010 14:55:56 -0500

forwarded 591293 http://bugs.bacula.org/view.php?id=1623
thanks

In update_postgresql_tables.in, there is:

CREATE INDEX file_jpfid_idx on File (JobId, PathId, FilenameId);

And at http://bugs.debian.org/591293 I received a bug report indicating 
that upgrades were failing with this message:

ERROR:  relation "file_jpfid_idx" already exists

Now, investigating a bit...

In the 5.0.2 source tree, updatedb/update_postgresql_tables_7_to_8 
contains this line:

create index file_jpfid_idx on file (jobid, pathid, filenameid);

In the 3.0.3 source tree, src/cats/make_postgresql_tables.in containts 
this line:

CREATE INDEX file_jpfid_idx on file (jobid, pathid, filenameid);

However, it was commented out in your distribution in 2.4.4 (but 
uncommented for Debian).

So it seems like people that installed fresh with 3.0.0 or later will 
already have the index and thus the upgrade will fail.  Those that 
started with 2.4.4 will not have the index and will get it.  But, of 
course, those that started with 1.34 will also fail because it was added 
for them with the upgrade to 1.35.

It seems that there may need to be some automated validation of these 
schema updates; see for instance also 
http://bugs.bacula.org/view.php?id=1498

Message #37 received at 591293@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: control@bugs.debian.org, 591293@bugs.debian.org

Subject: Severity serious

Date: Fri, 20 Aug 2010 14:58:15 -0500

severity 591293 serious
thanks

Setting serious as it appears that this may impact multiple people's 
upgrads.

Message #44 received at 591293-close@bugs.debian.org (full text, mbox, reply):

From: John Goerzen <jgoerzen@complete.org>

To: 591293-close@bugs.debian.org

Subject: Bug#591293: fixed in bacula 5.0.2-2

Date: Fri, 20 Aug 2010 20:48:04 +0000

Source: bacula
Source-Version: 5.0.2-2

We believe that the bug you reported is fixed in the latest version of
bacula, which is due to be installed in the Debian FTP archive:

bacula-client_5.0.2-2_all.deb
  to main/b/bacula/bacula-client_5.0.2-2_all.deb
bacula-common-mysql_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-common-mysql_5.0.2-2_amd64.deb
bacula-common-pgsql_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-common-pgsql_5.0.2-2_amd64.deb
bacula-common-sqlite3_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-common-sqlite3_5.0.2-2_amd64.deb
bacula-common_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-common_5.0.2-2_amd64.deb
bacula-console-qt_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-console-qt_5.0.2-2_amd64.deb
bacula-console_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-console_5.0.2-2_amd64.deb
bacula-director-common_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-director-common_5.0.2-2_amd64.deb
bacula-director-mysql_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-director-mysql_5.0.2-2_amd64.deb
bacula-director-pgsql_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-director-pgsql_5.0.2-2_amd64.deb
bacula-director-sqlite3_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-director-sqlite3_5.0.2-2_amd64.deb
bacula-director-sqlite_5.0.2-2_all.deb
  to main/b/bacula/bacula-director-sqlite_5.0.2-2_all.deb
bacula-fd_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-fd_5.0.2-2_amd64.deb
bacula-sd-mysql_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-sd-mysql_5.0.2-2_amd64.deb
bacula-sd-pgsql_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-sd-pgsql_5.0.2-2_amd64.deb
bacula-sd-sqlite3_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-sd-sqlite3_5.0.2-2_amd64.deb
bacula-sd-sqlite_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-sd-sqlite_5.0.2-2_amd64.deb
bacula-sd_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-sd_5.0.2-2_amd64.deb
bacula-server_5.0.2-2_all.deb
  to main/b/bacula/bacula-server_5.0.2-2_all.deb
bacula-traymonitor_5.0.2-2_amd64.deb
  to main/b/bacula/bacula-traymonitor_5.0.2-2_amd64.deb
bacula_5.0.2-2.diff.gz
  to main/b/bacula/bacula_5.0.2-2.diff.gz
bacula_5.0.2-2.dsc
  to main/b/bacula/bacula_5.0.2-2.dsc
bacula_5.0.2-2_all.deb
  to main/b/bacula/bacula_5.0.2-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 591293@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Goerzen <jgoerzen@complete.org> (supplier of updated bacula package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 20 Aug 2010 14:58:19 -0500
Source: bacula
Binary: bacula bacula-common bacula-common-sqlite3 bacula-common-pgsql bacula-common-mysql bacula-director-common bacula-director-sqlite bacula-director-sqlite3 bacula-director-mysql bacula-director-pgsql bacula-client bacula-fd bacula-server bacula-sd bacula-sd-sqlite3 bacula-sd-sqlite bacula-sd-mysql bacula-sd-pgsql bacula-console bacula-console-qt bacula-traymonitor
Architecture: source all amd64
Version: 5.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen <jgoerzen@complete.org>
Changed-By: John Goerzen <jgoerzen@complete.org>
Description: 
 bacula     - network backup, recovery and verification - meta-package
 bacula-client - network backup, recovery and verification - client meta-package
 bacula-common - network backup, recovery and verification - common support files
 bacula-common-mysql - network backup, recovery and verification - MySQL common files
 bacula-common-pgsql - network backup, recovery and verification - PostgreSQL common fil
 bacula-common-sqlite3 - network backup, recovery and verification - SQLite v3 common file
 bacula-console - network backup, recovery and verification - text console
 bacula-console-qt - Bacula Administration Tool Console
 bacula-director-common - network backup, recovery and verification - Director common files
 bacula-director-mysql - network backup, recovery and verification - MySQL storage for Dir
 bacula-director-pgsql - network backup, recovery and verification - PostgreSQL storage fo
 bacula-director-sqlite - network backup, recovery and verification - SQLite 2 director tra
 bacula-director-sqlite3 - network backup, recovery and verification - SQLite 3 storage for
 bacula-fd  - network backup, recovery and verification - file daemon
 bacula-sd  - network backup, recovery and verification - storage daemon
 bacula-sd-mysql - network backup, recovery and verification - MySQL SD tools
 bacula-sd-pgsql - network backup, recovery and verification - PostgreSQL SD tools
 bacula-sd-sqlite - network backup, recovery and verification - SQLite SD tools
 bacula-sd-sqlite3 - network backup, recovery and verification - SQLite 3 SD tools
 bacula-server - network backup, recovery and verification - server meta-package
 bacula-traymonitor - network backup, recovery and verification - tray monitor
Closes: 591293
Changes: 
 bacula (5.0.2-2) unstable; urgency=medium
 .
   * Remove spurious creation of file_jpfid_idx on upgrade.  Closes: #591293.
Checksums-Sha1: 
 bfabd1529059dead7587a9bfd07e17d9ebdb9ad6 1909 bacula_5.0.2-2.dsc
 d2dcd4e1a2a6f6209333e5e4f955144f8b76d6d2 42538 bacula_5.0.2-2.diff.gz
 569e27a76f9875b2d79ce3aabd048a59be695aef 1020 bacula_5.0.2-2_all.deb
 89caf003c9692ac0aa002937dffcd436e5245e9f 48234 bacula-director-sqlite_5.0.2-2_all.deb
 427a7daa75d174279ba51477c2d8818b8d57bdb3 48260 bacula-client_5.0.2-2_all.deb
 0fbab4a069bce812193d750f13026f46114f3b11 48182 bacula-server_5.0.2-2_all.deb
 49e9151e30ab463b1cd8f00aab9e650a70e2b95a 637688 bacula-common_5.0.2-2_amd64.deb
 2fa25cf2a6e6a187249771ed806f6d6f122b2ff4 101966 bacula-common-sqlite3_5.0.2-2_amd64.deb
 9e3f3d37131caa21b96fee8338737c187ec91255 106116 bacula-common-pgsql_5.0.2-2_amd64.deb
 e67eef9ad56501e39875c6bf92f68c63d8a5f00e 101968 bacula-common-mysql_5.0.2-2_amd64.deb
 a07651bf5da740d252d2c10355fd80dba795b97e 56876 bacula-director-common_5.0.2-2_amd64.deb
 3e800b76354b7bcaae819b7edc0a9a3bf981f79e 308052 bacula-director-sqlite3_5.0.2-2_amd64.deb
 0197e79351fab5c5324958fdce45b8274410475f 308298 bacula-director-mysql_5.0.2-2_amd64.deb
 08426ecddfaab9f68fb2d6d8527ea12251c187a3 308392 bacula-director-pgsql_5.0.2-2_amd64.deb
 27a505a386053f97d90e6597d5836f03d66a231f 124364 bacula-fd_5.0.2-2_amd64.deb
 bdb848466bf9b8cbd80e00913c32f9c6f78003a4 459476 bacula-sd_5.0.2-2_amd64.deb
 35c91edcdf5268f54c0acead3e7c5174de0c0ba6 435292 bacula-sd-sqlite3_5.0.2-2_amd64.deb
 e9129b4bb3364f3011cb1dfa43794a59384c08cb 48172 bacula-sd-sqlite_5.0.2-2_amd64.deb
 096002d1368b1831f3e083600bcdc53c10161033 435334 bacula-sd-mysql_5.0.2-2_amd64.deb
 00feec13cd19df90543ce31679de0788041cf53f 435344 bacula-sd-pgsql_5.0.2-2_amd64.deb
 8b35e5efcb926e3917286899d17d60bc667a77c9 67642 bacula-console_5.0.2-2_amd64.deb
 4f1d19fc3cb464f117080b8f5c0dec3b2911661a 648992 bacula-console-qt_5.0.2-2_amd64.deb
 50803da9c385f119749b3e6b19d060cf942d580f 70086 bacula-traymonitor_5.0.2-2_amd64.deb
Checksums-Sha256: 
 aaf0319d8a8fd2bd51fe4c1df6331cf016c1edf4cc1cf26bbcab12a42fe4f7d3 1909 bacula_5.0.2-2.dsc
 c6507c445bd998ff8cb5a03ed0ff8f99053849bf4d4de61c9e51c4079c372d90 42538 bacula_5.0.2-2.diff.gz
 bb2e550d89029ac2ccf57afecb7990126c58c8ba4afa02669a25e13b91ebbc01 1020 bacula_5.0.2-2_all.deb
 84cd62ca4773ca89929f3ef5049906689ab104c62f41dda2e9adece4b4d3c263 48234 bacula-director-sqlite_5.0.2-2_all.deb
 ee9f20b40896b6a5fa7dc7ffebaccdfa1e5b185085de50024d9a28f13c317b65 48260 bacula-client_5.0.2-2_all.deb
 323c9c88723029ee117773079e6fb3135ec802f5ab352378ca63df089bc02a6b 48182 bacula-server_5.0.2-2_all.deb
 0d6d186b22e8b99ff101bb8f216d3e20e012b77a71780daf58584fb920e9b549 637688 bacula-common_5.0.2-2_amd64.deb
 78e9d64b3e9bc7dcb9e409f01bc4a67c3fd68d03c7928626776e35417c10fbdb 101966 bacula-common-sqlite3_5.0.2-2_amd64.deb
 82422b2542eaa10e853affb5cc5c41fd750ed7ef249048f58d759c7bedbfb501 106116 bacula-common-pgsql_5.0.2-2_amd64.deb
 d7260f0236cf55fe8068034242cd30a8d19fed2eb6e3a9c639011c0731bc8286 101968 bacula-common-mysql_5.0.2-2_amd64.deb
 c3946e95059f431005af040fcba2756fb11fd982a01772b3ac014addb6f030dc 56876 bacula-director-common_5.0.2-2_amd64.deb
 e424b6454c7ac25308c7af63f4067376fdc2d1c9bd9567c53868c365e0feb4b3 308052 bacula-director-sqlite3_5.0.2-2_amd64.deb
 c72fa5bc478fc2d0eab7ab663d034f66bd29612ddc297cd5dcc15870e7180b07 308298 bacula-director-mysql_5.0.2-2_amd64.deb
 fb4d3ec5a71b2573ef8488e39d8081ca7579dcc28150839123d7ad63394bc2b9 308392 bacula-director-pgsql_5.0.2-2_amd64.deb
 95925155d9055f8b07a570d8c6f6f01465138edb03d9a7f65c6e3c0cbccd7232 124364 bacula-fd_5.0.2-2_amd64.deb
 7b80d80b0cba01f69d3d89dd408eb3bb81df4f0cf3acac0a54b416a9db240714 459476 bacula-sd_5.0.2-2_amd64.deb
 fdc5530c70848ff5441fa665d85f21a3df41bbc3993458f6883ce3f133140dd5 435292 bacula-sd-sqlite3_5.0.2-2_amd64.deb
 53b496ee14d5f4f622271e431a6949a5899690aa66e76a0ae55518a490050211 48172 bacula-sd-sqlite_5.0.2-2_amd64.deb
 b6ff6c8aa4de3ea67bd0379f8fa909a3782677f0561a1ce36449e00bc523c8e8 435334 bacula-sd-mysql_5.0.2-2_amd64.deb
 ed56bc407b3f327aa96362d93f143b82713fea6748ad83bb89eb598dd4ffbb80 435344 bacula-sd-pgsql_5.0.2-2_amd64.deb
 e5e9b949d7dd589c1ea27cae349fa953374a8378276d281ffcc5bd17295f48b9 67642 bacula-console_5.0.2-2_amd64.deb
 368a429e893738c4c64567ab0599981276b2e87a88a7ecf35e7e02b7e90a156a 648992 bacula-console-qt_5.0.2-2_amd64.deb
 bcf5d247486f501e83520f2ad7e245ea42f39c31fcf21398b5256ae5e6c608d9 70086 bacula-traymonitor_5.0.2-2_amd64.deb
Files: 
 7b9468b841cbcd6f70c59aceb3f5d323 1909 admin optional bacula_5.0.2-2.dsc
 33558b762c606730ceec74e57761d3d6 42538 admin optional bacula_5.0.2-2.diff.gz
 a259526a6bafc9b055232ee4e49c9dec 1020 admin optional bacula_5.0.2-2_all.deb
 a7799ae01b00ea10d3395cb6b01ce03d 48234 admin optional bacula-director-sqlite_5.0.2-2_all.deb
 00363c0961ca3af91a72f605a0993256 48260 admin optional bacula-client_5.0.2-2_all.deb
 d15abc4d191725c24304ca1c71c288e9 48182 admin optional bacula-server_5.0.2-2_all.deb
 a2e6b46689be473d93cc6f82a4875e36 637688 admin optional bacula-common_5.0.2-2_amd64.deb
 3c028a01f6e8496d0ec0eb937200e11f 101966 admin optional bacula-common-sqlite3_5.0.2-2_amd64.deb
 a9839fb9be0b44a9db02dcc81c8d5d1f 106116 admin optional bacula-common-pgsql_5.0.2-2_amd64.deb
 2dd67e217b2402121e6d5e801ee0aaa4 101968 admin optional bacula-common-mysql_5.0.2-2_amd64.deb
 cd0c351b20f647bc5e45757db18c3352 56876 admin optional bacula-director-common_5.0.2-2_amd64.deb
 d584bcb57c12ec1d203b94d48118bb0d 308052 admin optional bacula-director-sqlite3_5.0.2-2_amd64.deb
 532c1b80c76cfa0f414bcff5a07aa2ed 308298 admin optional bacula-director-mysql_5.0.2-2_amd64.deb
 b6c30638f0555fe214154f1440794032 308392 admin optional bacula-director-pgsql_5.0.2-2_amd64.deb
 05c870378addbbb4033646dd37d25896 124364 admin optional bacula-fd_5.0.2-2_amd64.deb
 6e0a0c50ef64423eca4f9703abd3c62f 459476 admin optional bacula-sd_5.0.2-2_amd64.deb
 4c429e74552d1cdf95c8edda06c7affb 435292 admin optional bacula-sd-sqlite3_5.0.2-2_amd64.deb
 a5681712d0dc838f8ea37b8fd69fa23d 48172 admin optional bacula-sd-sqlite_5.0.2-2_amd64.deb
 a2c940056f0ba3419908ec388f3b1d40 435334 admin optional bacula-sd-mysql_5.0.2-2_amd64.deb
 d397c1bc36f8238b701241cd4c431af1 435344 admin optional bacula-sd-pgsql_5.0.2-2_amd64.deb
 b0c4e630556125ba8a3787339b8e0ee1 67642 admin optional bacula-console_5.0.2-2_amd64.deb
 4706231f1eaf8b579040571fddbfa972 648992 utils optional bacula-console-qt_5.0.2-2_amd64.deb
 affa2ca880171f7cd57bba769136fbc3 70086 admin optional bacula-traymonitor_5.0.2-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkxu4wMACgkQ3PeFtIodmh9czACfRBlmh4cW0sY8bg3VzQz5DUbL
nv8AoMcfjHSrkgWX7x2d161+5QRCaQOO
=Rfsm
-----END PGP SIGNATURE-----

Message #49 received at 591293@bugs.debian.org (full text, mbox, reply):

From: Thomas Arendsen Hein <thomas@intevation.de>

To: John Goerzen <jgoerzen@complete.org>

Cc: 591293@bugs.debian.org

Subject: Re: Bug#591293: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Sat, 21 Aug 2010 22:00:26 +0200

* John Goerzen <jgoerzen@complete.org> [20100820 21:41]:
> On 08/20/2010 01:53 PM, Thomas Arendsen Hein wrote:
>>
>> 2010-08-01 21:58:55 upgrade bacula-director-pgsql 2.4.4-1 5.0.2-1~bpo50+1
>>
>> The history before that was that I used bacula-director-sqlite3
>> 2.2.8-8 in the past and switched to postgresql without
>> importing/converting the old catalog when bacula 2.4.2-3.1 was the
>> current version in lenny/testing. dbconfig-common is still at
>> 1.8.39:
>
> OK, let me restate that and make sure I understand correctly.
>
> 1. You used to use bacula-director-sqlite3 version 2.2.8-8.
>
> 2. At some point you installed bacula-director-pgsql 2.4.2-3.1 instead.
>
> 3. You started with a freshly-installed new catalog when you installed  
> 2.4.2-3.1, and made no effort to migrate the old catalog to it.
>
> 4. You made no changes to the database schema manually at any point.
>
> 5. You upgraded to 2.4.4-1 over time.
>
> 6. Then you had an error when upgrading from 2.4.4 to 5.0.2.
>
> Is that correct?

Yes, correct.

I'll try the change you have done in 5.0.2-2, i.e. removing the line

CREATE INDEX file_jpfid_idx on File (JobId, PathId, FilenameId);

from update_postgresql_tables.

Thanks,
Thomas

-- 
thomas@intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Message #54 received at 591293@bugs.debian.org (full text, mbox, reply):

From: Thomas Arendsen Hein <thomas@intevation.de>

To: John Goerzen <jgoerzen@complete.org>

Cc: 591293@bugs.debian.org

Subject: Re: Bug#591293: bacula-director-pgsql: db upgrade to lenny-backports fails with ERROR: relation "file_jpfid_idx" already exists

Date: Sat, 21 Aug 2010 22:22:46 +0200

* Thomas Arendsen Hein <thomas@intevation.de> [20100821 22:00]:
> I'll try the change you have done in 5.0.2-2, i.e. removing the line
> 
> CREATE INDEX file_jpfid_idx on File (JobId, PathId, FilenameId);
> 
> from update_postgresql_tables.

I noticed that this actually was nearly the last thing done during
the upgrade. I just manually executed "ANALYSE;" and I think my
database is in a sane state now. I verified that the changes done in
/usr/share/dbconfig-common/data/bacula-director-pgsql/upgrade/pgsql/5.0.0
are in the database and everything looks ok.

Thanks,
Thomas

-- 
thomas@intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Send a report that this bug log contains spam.