| From: | Helge Bahmann <bahmann(at)math(dot)tu-freiberg(dot)de> |
|---|---|
| To: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
| Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, mark Kirkwood <markir(at)slingshot(dot)co(dot)nz>, <pgsql-general(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Linux Largefile Support In Postgresql RPMS |
| Date: | 2002-08-09 07:51:54 |
| Message-ID: | Pine.LNX.4.44.0208090943170.6032-100000@lothlorien.stunet.tu-freiberg.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> As far as I can make out from the libc docs, largefile support is
> automatic if the macro _GNU_SOURCE is defined and the kernel supports
> large files.
>
> Is that a correct understanding? or do I actually need to do something
> special to ensure that pg_dump supports large files?
in this case you still have to use large file functions in the code
explicitly
the easiest way to get large file support is to pass
-D_FILE_OFFSET_BITS=64 to the preprocessor, and I think I remember doing
this once for pg_dump
see /usr/include/features.h
Best regards
Helge
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martina Mostert | 2002-08-09 09:32:34 | Re: C-function and query |
| Previous Message | Rob Brown-Bayliss | 2002-08-09 06:41:10 | oid's and primary keys on insert |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2002-08-09 08:21:20 | Re: Locale number format confusion |
| Previous Message | Dave Page | 2002-08-09 07:12:47 | Re: CLUSTER and indisclustered |