Re: pg_largeobject

Поиск
Список
Период
Сортировка
От Sridhar N Bamandlapally
Тема Re: pg_largeobject
Дата
Msg-id CAGuFTBVnZAiiGNgfhjFaC1MW_RhpfCojD+4Jhs9D2ruskMCJcQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_largeobject  (John R Pierce <pierce@hogranch.com>)
Ответы Re: pg_largeobject  (Alvaro Aguayo Garcia-Rada <aaguayo@opensysperu.com>)
Re: pg_largeobject  ("Daniel Verite" <daniel@manitou-mail.org>)
Список pgsql-general
Дерево обсуждения
all media files are stored in database with size varies from 1MB - 5GB

based on media file types and user-group we storing in different tables, but PostgreSQL store OID/Large-object in single table (pg_largeobject), 90% of database size is with table pg_largeobject

due to size limitation BYTEA was not considered

Thanks
Sridhar



On Tue, Mar 29, 2016 at 3:05 PM, John R Pierce <pierce@hogranch.com> wrote:
On 3/29/2016 2:13 AM, Sridhar N Bamandlapally wrote:
Hi

pg_largeobject is creating performance issues as it grow due to single point storage(for all tables)

is there any alternate apart from bytea ?

like configuration large-object-table at table-column level and oid PK(primary key) stored at pg_largeobject


 I would as soon use a NFS file store for larger files like images, audio, videos, or whatever.   use SQL for the relational metadata.

just sayin'....



--
john r pierce, recycling bits in santa cruz



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

В списке pgsql-general по дате отправления:

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Horrible/never returning performance using stable function on WHERE clause
Следующее
От: Achilleas Mantzios
Дата:
Сообщение: Re: Horrible/never returning performance using stable function on WHERE clause