Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis,amqp, s3 in the future? - Mailing list pgsql-general

From John R Pierce
Subject Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis,amqp, s3 in the future?
Date
Msg-id 59f9e56e-6b36-91ab-475d-1b3cb0df8694@hogranch.com
Whole thread Raw
In response to Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis,amqp, s3 in the future?  ("Sven R. Kunze" <srkunze@mail.de>)
Responses Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?  (Alan Hodgson <ahodgson@lists.simkin.ca>)
List pgsql-general
On 5/4/2017 2:08 PM, Sven R. Kunze wrote:
No.  You can certainly use PostgreSQL to store blobs.  But then, you need to store the PostgreSQL data **someplace**.
If you don't store it in S3, you have to store it somewhere else.

I don't understand what you mean here. AFAIK storing blobs in PG is not recommended since it is not very efficient.

Seems like several people here disagree with this conventional wisdom.

I think what he was talking about the data itself. You have to store the bits and bytes somewhere (e.g. on S3).


afaik, S3 is not suitable for the $PGDATA directory, its more of an archival block file store for sequential access.    for the actual database storage in the AWS world, you'd either use EC2 local storage, or EBS, and I've heard from more than a few people that EBS can be something of a sand trap.

re: storing blobs in postgres, I would be very hesitant to storage LARGE amounts of bulk data directly in postgres

-- 
john r pierce, recycling bits in santa cruz

pgsql-general by date:

Previous
From: "Sven R. Kunze"
Date:
Subject: Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis,amqp, s3 in the future?
Next
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis,amqp, s3 in the future?