Re: pg_dump and large files - is this a problem? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump and large files - is this a problem?
Date
Msg-id 14164.1036197104@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump and large files - is this a problem?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I think the problem is more accurately described thus:  Flex generated
> files include <stdio.h> before "postgres.h" due to the way it lays out the
> code in the output.  stdio.h does something which prevents switching to
> the large file model later on in postgres.h.  (This manifests itself in
> unistd.h, but unistd.h itself is not the problem per se.)

> The proposed fix was to include the flex output in some other file (such
> as the corresponding grammar file) rather than to compile it separately.

I have made this change.  CVS tip should compile cleanly now on machines
where this is an issue.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PG, Crystal Reports, Stored Procedures and User Defined
Next
From: Bruce Momjian
Date:
Subject: Re: calculated fields are not seen in the WHERE clause