| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: Removing pg_migrator limitations |
| Date: | 2009-12-25 06:17:35 |
| Message-ID: | 200912250617.nBP6HZM13399@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> > Well, we might eventually allow addition of values to enums too; the
> > fact that it's not implemented outside pg_migrator right now doesn't
> > mean we won't ever think of a solution. In any case I'm not persuaded
> > that a zero-element enum is totally without value. Think of it like a
> > domain with a "must be null" constraint.
>
> OK, but that is going to expand the my patch. I will probably implement
> zero-element enums first and then go ahead and do the binary upgrade
> part. Zero-element enums will simplify the pg_dump code.
I have implemented the zero-value option to CREATE TYPE ENUM with the
attached patch.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| Attachment | Content-Type | Size |
|---|---|---|
| /pgpatches/enum_opt | text/x-diff | 2.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-12-25 08:55:17 | Re: info about patch: using parametrised query in psql |
| Previous Message | Fujii Masao | 2009-12-25 05:33:58 | Re: Streaming Rep - 2-phase backups and reducing time to full replication |