Re: [HACKERS] pg_dump and INCREMENT BY
On Wed, 7 Apr 2004, Dennis Bjorklund wrote: Replying to myself here :-) wants to import it into a 7.3 database. Use the 7.3 dump you might say, but since BY does not do anything why not remove it from the dump output? I just realized there is yet another new construct in 7.4. The sequences are created with NO MAXVALUE (and MINVALUE). Couldn't these just be removed in the pg_dump output in this case. It's the default anyway, right. I just imported a fairly big dump from a 7.4 database into a 7.3 database and the sequences was the only thing I had to change. Of course the database in itself was designed on 7.3 so it didn't use any 7.4 features. It's not a big issue, it's just that it seems simple to dump SQL code (for sequences) that work the same on both 7.4 and older, not just 7.4. -- /Dennis Björklund ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] pg_dump and INCREMENT BY
Dennis Bjorklund [EMAIL PROTECTED] writes: I just realized there is yet another new construct in 7.4. The sequences are created with NO MAXVALUE (and MINVALUE). Couldn't these just be removed in the pg_dump output in this case. It's the default anyway, right. IIRC, these changes were to bring the syntax in line with the SQL200x spec, and thus possibly improve compatibility with other databases. I'm not eager to revert them. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] pg_dump and INCREMENT BY
On Wed, 7 Apr 2004, Dennis Bjorklund wrote: On Wed, 7 Apr 2004, Dennis Bjorklund wrote: Replying to myself here :-) wants to import it into a 7.3 database. Use the 7.3 dump you might say, but since BY does not do anything why not remove it from the dump output? I just realized there is yet another new construct in 7.4. The sequences are created with NO MAXVALUE (and MINVALUE). Couldn't these just be removed in the pg_dump output in this case. It's the default anyway, right. I just imported a fairly big dump from a 7.4 database into a 7.3 database and the sequences was the only thing I had to change. Of course the database in itself was designed on 7.3 so it didn't use any 7.4 features. It's not a big issue, it's just that it seems simple to dump SQL code (for sequences) that work the same on both 7.4 and older, not just 7.4. Maybe a switch to set the destination version would be a good compromise? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
