| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: building pg_dump doesn't work |
| Date: | 2009-03-05 13:13:31 |
| Message-ID: | 20090305131331.GB4087@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> Dne 3.03.09 22:55, Tom Lane napsal(a):
>
>>
>> One idea that comes to mind is to replace the entries like
>>
>> {"abort", ABORT_P, UNRESERVED_KEYWORD},
>>
>> with macro calls
>>
>> PG_KEYWORD("abort", ABORT_P, UNRESERVED_KEYWORD),
>>
>> and then the frontend build of the file could define the macro
>> to ignore its second argument.
>
> It sounds good.
Please have a look at the patch I just posted -- should be up in a few
minutes in
http://archives.postgresql.org/message-id/20090305131208.GA4087%40alvh.no-ip.org
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-03-05 13:23:13 | Re: building pg_dump doesn't work |
| Previous Message | Alvaro Herrera | 2009-03-05 13:12:08 | Re: building pg_dump doesn't work |