Re: Large objects.

From: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Large objects.
Date: 2010-09-27 18:25:04
Message-ID: AANLkTin3XrKsdx+YXgqQC+bMbzEe_yhBAncVQuS-SY7E@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 not so clean because I need to take into account the behavior
of lo_write() and 2GB limit.

--
// Dmitriy.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-27 19:11:07 Re: trailing whitespace in psql table output
Previous Message Gurjeet Singh 2010-09-27 18:20:21 Re: Improving prep_buildtree used in VPATH builds