Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Minor problems reloading dump in 7.0beta1

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Minor problems reloading dump in 7.0beta1
Date: 2000-02-24 15:18:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Hi!
> When upgrading a server from version 6.5.2 to 7.0beta1, we hit the following
> problems when reloading the data from pg_dumpall:
> - Is it a "known feature" that when using "psql -f pgfull.dump" it aborts on
> the "\connect" lines from pg_dumpall? The dump works fine if I start psql
> and use \i to load it. (I reliase the documentation says use "psql <
> filename", but I didn't read that far :-)

This is a new psql feature that scripts exit on first failure, I think.

> - It fails to reload datetime indexes, because of "DefineIndex: datetime_ops
> class not found". I take it this is because of the new datetime stuff, but
> it should at least be put into some notes somewhere that you have to tweak
> the pg_dump output for these.

We need to fix that somehow.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-hackers by date

Next:From: Karl DeBisschopDate: 2000-02-24 15:23:23
Previous:From: Peter EisentrautDate: 2000-02-24 15:12:04
Subject: Re: [HACKERS] Minor problems reloading dump in 7.0beta1

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group