From: | Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: bytea or large objects? |
Date: | 2005-08-26 17:12:25 |
Message-ID: | deniho$1asb$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Joshua D. Drake wrote:
>
>> I've just re-written our Whitebeam code to drop large-objects in
>> favour of BYTEA fields.
>>
>> All the old problems of large objects in backups exist, but the killer
>> for us was that none of the current replication systems, at least that
>> I could find, would replicate large objects. This became a mandatory
>> requirements for us.
>
> Mammoth Replicator has always replicated Large Objects. The only
> "backup" issue to large objects is that you have to pass a separate flag
> and use the custom or tar format to dump them.
>
> Bytea has its own issues mostly based around memory usage.
>
> I am not saying you should or shouldn't switch as it really depends on
> your needs but the information above just isn't quite accurate.
>
> Sincerely,
>
> Joshua D. Drake
>
I should have added that my search was limited to open source/free replication
systems.
>
>>
>> I'd have to have a *very* good reason to use large objects over BYTEA
>> now.
>>
>> Pete
>> --
>> http://www.whitebeam.org
>> http://www.yellowhawk.co.uk
>> -----
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 5: don't forget to increase your free space map settings
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-08-26 17:19:56 | Re: Serials jumping |
Previous Message | Matt A. | 2005-08-26 16:58:07 | Re: Serials jumping |