Re: pg_dump future problem. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump future problem.
Date
Msg-id 27609.1052057422@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump future problem.  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_dump future problem.
List pgsql-hackers
Philip Warner <pjw@rhyme.com.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump future problem.
Next
From: Shridhar Daithankar
Date:
Subject: Re: Slackware 9 Build Problems