| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Giles Lean <giles(at)nemeton(dot)com(dot)au> |
| Subject: | Re: pg_dump and large files - is this a problem? |
| Date: | 2002-10-24 02:37:49 |
| Message-ID: | 200210240237.g9O2bn400622@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Philip Warner wrote:
> At 10:03 PM 23/10/2002 -0400, Bruce Momjian wrote:
> >It is much cleaner to just duplicate the entire API so you don't have
> >any limitations or failure cases.
>
> We may still end up using macros in pg_dump to cope with cases where off_t
> & fseeko are not defined - if there are any. I presume we would then just
> revert to calling fseek/ftell etc.
Well, we have fseeko falling back to fseek already, so that is working
fine. I don't think we will find any OS's without off_t. We just need
a little smarts. Let me see if I can work on it now.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Giles Lean | 2002-10-24 02:54:50 | Re: pg_dump and large files - is this a problem? |
| Previous Message | Philip Warner | 2002-10-24 02:36:20 | Re: pg_dump and large files - is this a problem? |