Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Paul T. <pt...@wa...>]

Upgrading and restoring at the same time?  Seems a bit tricky to begin with.

If all else fails first restore to same version then do upgrades later. But
maybe this helps:

Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts before
letting postgres or SQL-Ledger have a second go?
If not i strongly suggest you do that, saved my ass in the past getting from
a blown 2.2 to a new 2.4 iirc..


2008/6/14 Michael Hasse <mh...@it...>:

> Not a complete answer but we've seen the TOC error after upgrades as
> some of the rights get reset and the user the dump is executing under
> doesn't have access.
>
>
> Thanks,
>
> Michael
>
> On Jun 14, 2008, at 11:14 AM, Stuart Luppescu wrote:
>
> > On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
> >> I've been putting off the upgrade as long as I could, but I
> >> finally gave
> >> it a go. However, when I log in after following the instructions,
> >> I get
> >> this error:
> >>
> >> Error!
> >>
> >> drop trigger del_recurring ON oe
> >> ERROR: trigger "del_recurring" for table "oe" does not exist
> >
> > Well, I just tried again and it worked (after I deleted the nologin
> > file). But then I found that my nightly backups using pg_dump and
> > restores to a mirror system stopped working about a week ago. I'm
> > getting these messages:
> >
> > pg_restore: [tar archiver] could not open TOC file for input: No such
> > file or directory
> >
> > The line that triggers this message is:
> > pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup
> >
> > The funny thing is that the backup file suddenly went from 4.1MB in
> > size
> > to 9.3MB on the day it stopped working. I had upgraded postgres from
> > 8.0.13 to 8.0.15 a few days previous, and then we had a power failure
> > and when the machine rebooted, these problems started.
> >
> > So, since my mirror was a week out of date, I got a backup file from
> > System -> Backup -> Save to file, and restored that to my mirror
> > system.
> > Then when I logged in I got this error message:
> >
> > Upgrading to Version 2.8.15 ...
> > Error!
> > create table cargo (id int not null, trans_id int not null, package
> > text, netweight float4, grossweight float4, volume float4)
> > ERROR: relation "cargo" already exists
> >
> > I REALLY need to get this working again. Any help will be greatly
> > appreciated.
> >
> > --
> > Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> > University of Chicago (^_^)/ CCSR
> > 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> > Respect is a rational process   -- McCoy, "The
> >  Galileo Seven", stardate 2822.3
> >
> >
> >
> >
> >
> > ----------------------------------------------------------------------
> > ---
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > _______________________________________________
> > sql-ledger-users mailing list
> > sql...@li...
> > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>