From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | James Sewell <james(dot)sewell(at)lisasoft(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_largeobjects |
Date: | 2013-09-11 13:14:21 |
Message-ID: | 1378905261.28606.YahooMailNeo@web162904.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
James Sewell <james(dot)sewell(at)lisasoft(dot)com> wrote:
> is there any reason to use pg_largeobjects if I am storing data
> under 1GB which doesn't require random reads any more?
If individual large objects might need to be referenced from
multiple locations, it gives you an easy way to do that without
needing to create a new table with id and document columns (and
possibly a comment column).
It gives you the ability to stream documents in rather than
including them in a SQL statement, which can reduce stress on RAM.
It gives you the ability to set the security for individual
documents, although it sounds like that is not something you find
useful.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Eduardo Morras | 2013-09-11 14:49:32 | Re: Call for design: PostgreSQL mugs |
Previous Message | John R Pierce | 2013-09-11 09:37:38 | Re: problem in installation of postgresql-jdbc |