| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Allow pg_dump to dump sequences using NO_MAXVALUE and NO_MINVALUEb |
| Date: | 2003-02-23 13:39:49 |
| Message-ID: | 1046007589.84130.102.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
- Move SEQ_MAXVALUE, SEQ_MINVALUE definitions to sequence.h
- Add check in pg_dump to see if the value returned is the max /min
values and replace with NO MAXVALUE, NO MINVALUE.
- Change START and INCREMENT to use START WITH and INCREMENT BY syntax.
This makes it a touch easier to port to other databases with sequences
(Oracle). PostgreSQL supports both syntaxes already.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| Attachment | Content-Type | Size |
|---|---|---|
| dbseqdump.patch | text/x-patch | 5.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2003-02-23 14:05:41 | Re: Allow pg_dump to dump sequences using NO_MAXVALUE and |
| Previous Message | Christopher Kings-Lynne | 2003-02-23 11:16:57 | Re: bug in contrib/adddepend |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2003-02-23 14:05:41 | Re: Allow pg_dump to dump sequences using NO_MAXVALUE and |
| Previous Message | Rod Taylor | 2003-02-23 13:22:28 | Information schema updates |