Re: Use of Serial Datatype and Sequence Issue

On Lun 05 Nov 2001 17:03, you wrote:
> The message may be a bit misleading. using a SERIAL data type actually
> means that you are implicitly creating a sequence. A sequence is a separate
> object, not tied to any column. Data type SERIAL is just shorthand for
> defining an INT4 column and a sequence object with a DEFAULT clause on the
> column calling the sequence. You can do this explicitly as well. The docs
> may not be clear about this relationship. Hence, you have to drop the
> sequences explicitly if you don't want them anymore.
>
> IMHO, when you do a data-only pg_dump as SQL inserts, the fact that SQL to
> create sequences is dumped as well seems a bug to me. Any plans to change
> this, Tom Lane?

Where's the bug? The inserts come with the value inserted into the INT column
(origanally SERIAL), so all that has to be taken care of is making the
sequence start where it is, which is the behaviour of pg_dump.

What would be great is a binary dump, with it's reload application, so that
BIG backups/restores could be done in a small amount of time.

Saludos... :-)

--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-----------------------------------------------------------------
Martín Marqués                  |        mmarques@unl.edu.ar
Programador, Administrador, DBA |       Centro de Telematica
                       Universidad Nacional
                            del Litoral
-----------------------------------------------------------------