Re: postgreSQL 7.3.8, pg_dump not able to find large o

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Ron Snyder <snyder(at)roguewave(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: postgreSQL 7.3.8, pg_dump not able to find large o
Date: 2005-06-09 18:48:33
Message-ID: 21898.1118342913@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Joshua D. Drake" <jd(at)commandprompt(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dianne Yumul 2005-06-09 19:23:48 Re: Postgresql fails to start? (Update)
Previous Message Joshua D. Drake 2005-06-09 18:10:07 Re: postgreSQL 7.3.8, pg_dump not able to find large o