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

From Zeugswetter Andreas SB SD
Subject Re: pg_dump and large files - is this a problem?
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4961ED6@m0114.s-mxs.net
Whole thread Raw
In response to pg_dump and large files - is this a problem?  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_dump and large files - is this a problem?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > The problem with flex is, that the generated c file does #include <unistd.h>
> > before we #include "postgres.h".
> > In this situation _LARGE_FILES is not defined for unistd.h and unistd.h
> > chooses to define _LARGE_FILE_API, those two are not compatible.
>
> Yeah.  AFAICS the only way around this is to avoid doing any I/O
> operations in the flex-generated files.  Fortunately, that's not much
> of a restriction.

Unfortunately I do not think that is sufficient, since the problem is already
at the #include level. The compiler barfs on the second #include <unistd.h>
from postgres.h

Andreas


pgsql-hackers by date:

Previous
From: Pedro Miguel Frazao Fernandes Ferreira
Date:
Subject: Re: float output precision questions
Next
From: Tom Lane
Date:
Subject: Re: pg_dump and large files - is this a problem?