| From: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
|---|---|
| To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org>, PostgreSQL-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pg_largeobject |
| Date: | 2016-03-29 09:13:45 |
| Message-ID: | CAGuFTBU2RNmncbn8ZMPx0y3vgxtxAd1+rGk8yX503CndJL9AcQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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
Thanks
Sridhar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-03-29 09:35:01 | Re: pg_largeobject |
| Previous Message | Roman Scherer | 2016-03-29 08:30:49 | Re: How to quote the COALESCE function? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ullrich | 2016-03-29 09:28:05 | Re: [COMMITTERS] pgsql: Sync tzload() and tzparse() APIs with IANA release tzcode2016c. |
| Previous Message | Oleg Bartunov | 2016-03-29 09:00:50 | Re: Draft release notes for next week's releases |