Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > My point is that it seems fsetpos is the approved way of accessing large
> > files, rather than fseeko. In fact, I don't have fseeko here but I do
> > have fsetpos, and it does handle large files because my includes have
> > this:
> >
> >
Bruce Momjian writes:
> My point is that it seems fsetpos is the approved way of accessing large
> files, rather than fseeko. In fact, I don't have fseeko here but I do
> have fsetpos, and it does handle large files because my includes have
> this:
>
> typedef off_t fpos_t
> typedef
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> If the {s|g}etrlimit warnings are indeed the only ones (i.e., none about
> open, fseek, write, read, etc.) then this is either a bug or there's
> something wrong in the include file order or something like that.
No such luck. Here's a more complete
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > Also, even with configure --disable-largefile, I find that pg_config.h
> > still contains
> >
> > /* Define to 1 to make fseeko visible on some hosts. */
> > #define _LARGEFILE_SOURCE 1
> >
> > /* Define to 1 if fseeko (and presumably ftello) exist
Tom Lane writes:
> /usr/include/sys/resource.h: In function `getrlimit':
> /usr/include/sys/resource.h:168: warning: implicit declaration of function
>`__getrlimit64'
> /usr/include/sys/resource.h: In function `setrlimit':
> /usr/include/sys/resource.h:170: warning: implicit declaration of funct
Tom Lane writes:
> Also, even with configure --disable-largefile, I find that pg_config.h
> still contains
>
> /* Define to 1 to make fseeko visible on some hosts. */
> #define _LARGEFILE_SOURCE 1
>
> /* Define to 1 if fseeko (and presumably ftello) exists and is declared. */
> #define HAVE_FSEEK
Tatsuo Ishii writes:
> Are you sure that backend gains more performance than 1GB segmented
> file (I mean large file support turn on LET_OS_MANAGE_FILESIZE)?
No idea. My change only enables access to large files, it doesn't change
the segmentation logic in the backend. The main use at this poi
> Large file support is now compiled by default if available. (Use
> --disable-largefile to turn it off. That's what Autoconf gives us.)
Are you sure that backend gains more performance than 1GB segmented
file (I mean large file support turn on LET_OS_MANAGE_FILESIZE)? I
myself have not tried y
Also, even with configure --disable-largefile, I find that pg_config.h
still contains
/* Define to 1 to make fseeko visible on some hosts. */
#define _LARGEFILE_SOURCE 1
/* Define to 1 if fseeko (and presumably ftello) exists and is declared. */
#define HAVE_FSEEKO 1
This strikes me as probably
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Large file support is now compiled by default if available.
I am now getting (on HPUX 10.20)
/usr/include/sys/resource.h: In function `getrlimit':
/usr/include/sys/resource.h:168: warning: implicit declaration of function
`__getrlimit64'
/usr/inclu
10 matches
Mail list logo
