| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_largeobject |
| Date: | 2016-03-29 09:35:01 |
| Message-ID: | 56FA4C45.1030003@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2016-03-29 10:47:40 | Re: More correlated (?) index woes |
| Previous Message | Sridhar N Bamandlapally | 2016-03-29 09:13:45 | pg_largeobject |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artur Zakirov | 2016-03-29 09:54:01 | Re: IF (NOT) EXISTS in psql-completion |
| Previous Message | Christian Ullrich | 2016-03-29 09:28:05 | Re: [COMMITTERS] pgsql: Sync tzload() and tzparse() APIs with IANA release tzcode2016c. |