Re: pg_dump's checkSeek() seems inadequate
От | Tom Lane |
---|---|
Тема | Re: pg_dump's checkSeek() seems inadequate |
Дата | |
Msg-id | 6345.1277691861@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_dump's checkSeek() seems inadequate (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: pg_dump's checkSeek() seems inadequate
|
Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> writes: > Tom Lane wrote: >> A somewhat more plausible scenario is that somebody might hope that >> they could do something like this: >> >> echo 'some custom header' >pg.dump >> pg_dump -Fc >>pg.dump > What would anyone hope to achieve by such a manoeuvre, even if it > worked, which I am close the dead sure it would not? It looks to me like it probably would actually work, so far as pg_dump is concerned, but _discoverArchiveFormat() would break it because that tries to do an unconditional fseeko(fp, 0, SEEK_SET) (and the position counting is screwed up even if the fseeko fails). That could probably be fixed if anyone thought this scenario was interesting enough to justify work directed specifically at it. I did the ftello/fseeko dance in checkSeek() just now because it seems sensible to me to have checkSeek() actually verify functionality of both of those calls, not because I think it's real likely that the position won't be 0. regards, tom lane
В списке pgsql-hackers по дате отправления: