Re: pg_dump future problem.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump future problem.
Date: 2003-05-04 14:10:22
Message-ID: 27609.1052057422@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> My preference for a solution to this problem would be to remove even more
> implementation knowledge from pg_dump, and add a command like:
> alter table really_long_name set next a = <next sequence value>;

And the is_called flag fits into this where?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shridhar Daithankar 2003-05-04 14:27:21 Re: Slackware 9 Build Problems
Previous Message Tom Lane 2003-05-04 14:01:45 Re: pg_dump future problem.