hi,
> On Sat, Apr 30, 2011 at 2:58 PM, Kevin Grittner
> wrote:
>> This is related to the "SIREAD lock versus ACCESS EXCLUSIVE lock"
>> thread, but seemed different enough to merit spinning off a new
>> thread.
>>
>> Our shop hasn't used large objects so far because of the lack of
>> security (unt
YAMAMOTO Takashi wrote:
> is there any chance to "just" make large objects obey the normal
> semantics in future?
I sure hope so, but I have no idea how hard that is. I feel the same
about TRUNCATE TABLE now that I recognize the semantic difference
between it and DELETE FROM with no WHERE cla
On Sat, Apr 30, 2011 at 2:58 PM, Kevin Grittner
wrote:
> This is related to the "SIREAD lock versus ACCESS EXCLUSIVE lock"
> thread, but seemed different enough to merit spinning off a new
> thread.
>
> Our shop hasn't used large objects so far because of the lack of
> security (until 9.1), so I n
On Mon, Sep 27, 2010 at 2:25 PM, Dmitriy Igrishin wrote:
> Hey Robert, Tom
>
> Tom, thank you for explanation!
>
>> Ouch. Letting people write data to where they can't get it back from
>> seems double-plus ungood.
>>
> Robert, yes, I agree with you. This is exactly what I wanted to say.
> I've im
Hey Robert, Tom
Tom, thank you for explanation!
Ouch. Letting people write data to where they can't get it back from
> seems double-plus ungood.
>
> Robert, yes, I agree with you. This is exactly what I wanted to say.
I've implemented a stream class in C++ and this circumstance makes
the code no
On Mon, Sep 27, 2010 at 10:50 AM, Tom Lane wrote:
> Robert Haas writes:
>> According to the documentation, the maximum size of a large object is
>> 2 GB, which may be the reason for this behavior.
>
> In principle, since pg_largeobject stores an integer pageno, we could
> support large objects of
Robert Haas writes:
> According to the documentation, the maximum size of a large object is
> 2 GB, which may be the reason for this behavior.
In principle, since pg_largeobject stores an integer pageno, we could
support large objects of up to LOBLKSIZE * 2^31 bytes = 4TB without any
incompatible
On Sun, Sep 26, 2010 at 12:21 PM, Dmitriy Igrishin wrote:
> Yes, I am sure. I've tested it by test case in my original post.
> Do you can compile and reproduce it please?
I think the reason lo_read is returning 0 is because it's not reading
anything. See attached test case, cleaned up a bit from
Hey Robert,
Yes, I am sure. I've tested it by test case in my original post.
Do you can compile and reproduce it please?
--
// Dmitriy.
On Fri, Sep 24, 2010 at 9:13 AM, Dmitriy Igrishin wrote:
> Tell me please, why lo_write() returns me the number of bytes "actually
> written"
> when current write location is out of 2GB ? IMO, in this case it should
> returns
> at least zero.
> lo_read() returns zero in this case, and it is correc
Bojidar Mihajlov wrote:
Hi all!
I need to operate with large objects through ODBC in
C/C++ program. How can I do that?
Look at the contrib lo data type.
Sincerely,
Joshua D. Drake
__
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.
Note, primary list address changed to -general, I'd suggest any followups
remove the -hackers, which I've left in just for 'closure'.
On Fri, 6 Jun 2003, Nigel J. Andrews wrote:
> On Fri, 6 Jun 2003, Tom Lane wrote:
>
> > "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > > Now, I did a little
Repost just to add the information that this is [now] on 7.3.3, previously on
7.3.2.
Sorry for the noise of the incomplete previous message, although the email
lists seem to be very light this last week. Obviously the mail server is still
feeling under the weather, I presume many posts have been
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> Now, I did a little bit of testing and when doing a \lo_export
> in psql connected via localhost a SIGPIPE is generated in
> write() in libc and psql quit, without printing any message to the
> terminal. Perhaps interestingly
> the file that gets
On Fri, 6 Jun 2003, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > Now, I did a little bit of testing and when doing a \lo_export
> > in psql connected via localhost a SIGPIPE is generated in
> > write() in libc and psql quit, without printing any message to the
> > termina
On Wed, Sep 19, 2001 at 12:46:03AM +0530, Chamanya wrote:
> Can I use ecpg with large objects? All examples in documentation are for
> libpq.
Yes and no. Since ECPG uses libpq it should not be too difficult to use the
lo functions too. But there is no way to use them via some EXEC SQL
statements
Hi,
> I had PostgreSQL 7.0.3 (7.1 now) and one nice day I've noticed that much
> number of my BLOBs are broken! Although they seems to be with good content
> in file system (xinv[0-9]+ files) I was not able to get them via
> lo_export... After spending some time trying to fix it, I decided to wri
17 matches
Mail list logo
