Skip site navigation (1) Skip section navigation (2)

Re: pg_dump and large files - is this a problem?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"Peter Eisentraut" <peter_e(at)gmx(dot)net>,"Philip Warner" <pjw(at)rhyme(dot)com(dot)au>,"PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>,"Giles Lean" <giles(at)nemeton(dot)com(dot)au>
Subject: Re: pg_dump and large files - is this a problem?
Date: 2002-10-28 18:15:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> 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.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-10-28 18:22:00
Subject: Re: [HACKERS] Request for supported platforms
Previous:From: Larry RosenmanDate: 2002-10-28 17:36:26
Subject: Re: [ANNOUNCE] Server downtime ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group