Re: Getting rid of some more lseek() calls
От
Alvaro Herrera
Тема
Re: Getting rid of some more lseek() calls
Дата
Msg-id
20200212163025.GA8864@alvherre.pgsql
Ответ на
Re: Getting rid of some more lseek() calls (Thomas Munro)
Список
Дерево обсуждения
Getting rid of some more lseek() calls Thomas Munro <thomas.munro@gmail.com>
Re: Getting rid of some more lseek() calls Andres Freund <andres@anarazel.de>
Re: Getting rid of some more lseek() calls Thomas Munro <thomas.munro@gmail.com>
Re: Getting rid of some more lseek() calls Michael Paquier <michael@paquier.xyz>
Re: Getting rid of some more lseek() calls Thomas Munro <thomas.munro@gmail.com>
Re: Getting rid of some more lseek() calls Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Getting rid of some more lseek() calls Thomas Munro <thomas.munro@gmail.com>
Re: Getting rid of some more lseek() calls Michael Paquier <michael@paquier.xyz>
Re: Getting rid of some more lseek() calls Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Getting rid of some more lseek() calls Thomas Munro <thomas.munro@gmail.com>
On 2020-Feb-12, Thomas Munro wrote: > Hmm. Well, on Unix we have to choose between "tell me the size but > also change the position that I either don't care about or have to > undo", and "tell me the size but also tell me all this other stuff I > don't care about". Since Windows apparently has GetFileSizeEx(), why > not use that when that's exactly what you want? It apparently > understands large files. I was already thinking that it might be better to make the new function just "tell me the file size" without leaking the details of *how* we do it, before reading about this Windows call. That reinforces it, IMO. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата: