From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: building pg_dump doesn't work |
Date: | 2009-03-05 09:48:11 |
Message-ID: | 49AF9FDB.1010702@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
> The way we do it now seems to have other disadvantages too: we are
> incorporating a backend .o file into pg_dump as-is, which would lead
> to large problems if there were differences in say the compiler flags
> needed. In fact, I thought Zdenek had been working on decoupling
> that sort of thing, so I'm a bit surprised it's still like this at all.
Yeah, it is still on my TODO list. There is still problem with
pg_resetxlog which needs lot of internals headers. :(
Zdenek
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-03-05 10:52:23 | Re: SIGHUP during recovery |
Previous Message | Simon Riggs | 2009-03-05 09:28:21 | Re: SIGHUP during recovery |