Re: [HACKERS] Backend problem with large objects
От | Ian Grant |
---|---|
Тема | Re: [HACKERS] Backend problem with large objects |
Дата | |
Msg-id | Pine.OSF.3.96.990202203715.13580A-100000@hotei.amtp.cam.ac.uk обсуждение исходный текст |
Ответ на | Re: [HACKERS] Backend problem with large objects (Tatsuo Ishii <t-ishii@sra.co.jp>) |
Ответы |
Re: [HACKERS] Backend problem with large objects
|
Список | pgsql-hackers |
On Tue, 2 Feb 1999, Tatsuo Ishii wrote: > Reproduced here too. Seems very old and known problem of large object > (writing into in the middle of a large object does not work). Many thanks, does this mean it's not likely to be fixed? If so I'll take this to the documentation list, if there is one. But first, can anyone explain what *is* allowed in lo_write after lo_lseek? Is it OK to overwrite a large object for example? I also note that there is no way to truncate a large object without reading the beginning bit and copying it out to another new large object, which involves it going down the wire to the client and then back again. Are there any plans to implement lo_trunc or something? Perhaps this is difficult for the same reason lo_write is difficult inside a large object. Ian
В списке pgsql-hackers по дате отправления: