Re: pg_dump versus SERIAL, round N

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org, Morus Walter <morus(dot)walter(at)experteer(dot)de>
Subject: Re: pg_dump versus SERIAL, round N
Date: 2006-08-19 20:01:21
Message-ID: 9142.1156017681@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> The only complaint I can see is that someone
> who wants pg_dump to dump out SERIAL so it appears just as he created
> the table, doesn't get that. Could we have pg_dump do that if the
> sequences all match the creation (weren't modified)?

pg_dump's output is often very far from what you typed in anyway.
My response to that person would be "get a life" ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-19 22:13:42 DROP OWNED BY doesn't work
Previous Message Bruce Momjian 2006-08-19 19:25:59 Re: pg_dump versus SERIAL, round N