Re: postgreSQL 7.3.8, pg_dump not able to find large o - Mailing list pgsql-general

From Tom Lane
Subject Re: postgreSQL 7.3.8, pg_dump not able to find large o
Date
Msg-id 21898.1118342913@sss.pgh.pa.us
Whole thread Raw
In response to Re: postgreSQL 7.3.8, pg_dump not able to find large o  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
"Joshua D. Drake" <jd@commandprompt.com> writes:
>> The question from the previous mail still stands: would anybody's
>> applications be broken if we change the MVCC behavior of large objects?

> Could you provide an instance where it might? I had always assumed (I
> know, never assume) that large objects were MVCC safe. All of our
> applications that work with binary data always use Large Objects.

It seems likely that such a change would fix more things than it broke,
in any case.  I'm just giving people a fair chance to object ;-)

            regards, tom lane

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: postgreSQL 7.3.8, pg_dump not able to find large o
Next
From: Dianne Yumul
Date:
Subject: Re: Postgresql fails to start? (Update)