Re: pg_dump and large files - is this a problem?
| От | Peter Eisentraut |
|---|---|
| Тема | Re: pg_dump and large files - is this a problem? |
| Дата | |
| Msg-id | Pine.LNX.4.44.0210231933410.928-100000@localhost.localdomain обсуждение исходный текст |
| Ответ на | Re: pg_dump and large files - is this a problem? (Bruce Momjian <pgman@candle.pha.pa.us>) |
| Ответы |
Re: pg_dump and large files - is this a problem?
Re: pg_dump and large files - is this a problem? |
| Список | pgsql-hackers |
Bruce Momjian writes: > I think you are right that we have to not use off_t and use long if we > can't find a proper 64-bit seek function, but what are the failure modes > of doing this? Exactly what happens for larger files? First we need to decide what we want to happen and after that think about how to implement it. Given sizeof(off_t) > sizeof(long) and no fseeko(), we have the following options: 1. Disable access to large files. 2. Seek in some other way. What's it gonna be? -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления: