| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: extensible enums |
| Date: | 2010-08-26 09:56:23 |
| Message-ID: | 4C763A47.1000105@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/26/2010 05:24 AM, Andrew Dunstan wrote:
>
>
> On 08/25/2010 03:29 AM, Andrew Dunstan wrote:
>>
>>
>> I've just been taking another look at this suggestion. I think it
>> will work quite cleanly. As long as we add the enums in the correct
>> order it should just do the Right Thing (tm).
>>
>> To answer your other question, Oid wraparound will not be a problem.
>>
>> Will get coding.
>>
>>
>
> Revised patch with pg_dump and pg_upgrade support is attached.
>
>
>
This time in context diff format.
cheers
andrew
| Attachment | Content-Type | Size |
|---|---|---|
| venum2.patch | text/x-patch | 108.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2010-08-26 10:07:00 | Re: bg worker: patch 1 of 6 - permanent process |
| Previous Message | Dimitri Fontaine | 2010-08-26 09:54:49 | Re: EXPLAIN doesn't show the actual function expression for FunctionScan |