pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrei Bintintan <klodoma@ar-sd.net>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump doesn't save correct the sequences
Date: Thu, 28 Oct 2004 19:51:32 +0300
Message-ID: <003101c4bd0e$61108180$0b00a8c0@forge> (raw)
References: <025201c4bcb1$fb556f10$0b00a8c0@forge>
	<20041027231815.Q66903@megazone.bigpanda.com>

Okay, If I modify all the Sequences in the dump, everything works fine.
Is there any possibility to specify to the pg_dump to save the sequences
with the "old" type??? I mean not with No MAXVALUE and No Minvalue???

My problem is that the 7.3 database I cannot "update" it for the moment for
diverse reasons, and I would like not to modify any dump anymore.

A strange thing is that this type of dump already worked once....



----- Original Message -----
From: "Stephan Szabo" <sszabo@megazone.bigpanda.com>
To: "Andrei Bintintan" <klodoma@ar-sd.net>
Cc: <pgsql-admin@postgresql.org>
Sent: Thursday, October 28, 2004 9:22 AM
Subject: Re: [ADMIN] pg_dump doesn't save correct the sequences


>
> On Thu, 28 Oct 2004, Andrei Bintintan wrote:
>
> > I try to dump a database from a 7.4.2 postgre system and to import it on
> > a 7.3.2. system, but I have a problem with the sequences in the dump.
>
> In general, the above is not guaranteed to work. pg_dump will use features
> of the dumping version so moving the dump to an earlier version is filled
> with danger.
>
> > This is a seq example:
> >
> > CREATE SEQUENCE test_id_seq
> >     INCREMENT BY 1
> >     NO MAXVALUE
> >     NO MINVALUE
> >     CACHE 1;
> >
> > This gives me an error when restoring on the 7.3 machine.
>
> Looking at the documentation, it looks like NO MAXVALUE and NO MINVALUE
> were added in 7.4.
>
> > I don't know what happened, because last week I also put a dump from 7.4
> > to 7.3 without any problems.
>
> > A coelege from me made an application and some modifications in the 7.4
> > database system, now I see that in every database there are these tables
> > that weren't before: sql_features, sql_implementation_info,
> > sql_languages, sql_packages, sql_sizing, sql_sizing_profiles.
>
> I believe these are part of the SQL standard information_schema.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>





view thread (3+ messages)

Message-ID: <003101c4bd0e$61108180$0b00a8c0@forge>
Permalink:  ../003101c4bd0e$61108180$0b00a8c0@forge/
Also on:    postgresql.org/message-id/003101c4bd0e$61108180$0b00a8c0@forge

 · 

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: klodoma@ar-sd.net, sszabo@megazone.bigpanda.com
  Subject: Re: pg_dump doesn't save correct the sequences
  In-Reply-To: <003101c4bd0e$61108180$0b00a8c0@forge>
  References: <025201c4bcb1$fb556f10$0b00a8c0@forge> <20041027231815.Q66903@megazone.bigpanda.com> <003101c4bd0e$61108180$0b00a8c0@forge>

* 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