pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Levy <dvid.levy@gmail.com>
To: Jerry Sievers <jerry@jerrysievers.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_restore index/trigger restoration issue
Date: Thu, 27 Apr 2006 14:06:24 +0200
Message-ID: <52543fce0604270506w1a039533m5183000e610c8be9@mail.gmail.com> (raw)
In-Reply-To: <m3mze7mebw.fsf@prod01.jerrysievers.com>
References: <52543fce0604270359u7b2bac2cgd1e4cb93245bd245@mail.gmail.com>
	<m3mze7mebw.fsf@prod01.jerrysievers.com>

I am using pgAdmin and phpPgAdmin with the same results (no triggers, no
indexes).

Thanks but the docs were not helpful yet. I've been trying to solve the
issue many times in the past few monthes before posting to the list today.
:(



On 27 Apr 2006 07:45:55 -0400, Jerry Sievers <jerry@jerrysievers.com> wrote:
>
> "David Levy" <dvid.levy@gmail.com> writes:
>
> > So I am trying to restore a pg_dump (version8.1 ) sql dump file from
> > a remote 8.0.3 DB into a local 8.1 DB using pg_restore (version
> > 8.1). Is there something incompatible The dump file seems to be
> > correct regarding index creation statements I really don't
> > understand what is happening As the title mentions, I have the same
> > issue with triggers : none of my triggers are restored neither ! Is
> > there any option in pg_dump or pg_restore to handle this
>
> Any chance your psql had the \t (show only tuples) option set?  This
> prevents seeing indexes and trigs in the table schema listing.
>
> As for what opts pg_dump and pg_restore offer, see the manual.
>
>
>
> -------------------------------------------------------------------------------
> Jerry Sievers   305 854-3001 (home)     WWW ECommerce Consultant
>                 305 321-1144 (mobile    http://www.JerrySievers.com/
>



--
David LEVY {selenium}
Website ~ http://www.davidlevy.org
Wishlist ZLiO ~ http://david.zlio.com/wishlist
Blog ~ http://selenium.blogspot.com


view thread (4+ messages)

Message-ID: <52543fce0604270506w1a039533m5183000e610c8be9@mail.gmail.com>
Permalink:  ../52543fce0604270506w1a039533m5183000e610c8be9@mail.gmail.com/
Also on:    postgresql.org/message-id/52543fce0604270506w1a039533m5183000e610c8be9@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: dvid.levy@gmail.com, jerry@jerrysievers.com
  Subject: Re: pg_restore index/trigger restoration issue
  In-Reply-To: <52543fce0604270506w1a039533m5183000e610c8be9@mail.gmail.com>
  References: <52543fce0604270359u7b2bac2cgd1e4cb93245bd245@mail.gmail.com> <m3mze7mebw.fsf@prod01.jerrysievers.com> <52543fce0604270506w1a039533m5183000e610c8be9@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox