From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Execute commands in single-user mode |
Date: | 2016-01-10 21:44:17 |
Message-ID: | VisenaEmail.9.cb4d3321c48f8ef2.1522d7c5e40@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På søndag 10. januar 2016 kl. 22:38:05, skrev Jim Nasby <
Jim(dot)Nasby(at)BlueTreble(dot)com <mailto:Jim(dot)Nasby(at)BlueTreble(dot)com>>:
On 1/10/16 10:01 AM, Andreas Joseph Krogh wrote:
> pg_largeobject being a system-relation does quite make sense to me, but
> that's another discussion. I know there has been some discussions in the
> past about making it a non system-relation but it never got anywhere AFAIK.
BTW, there's some other issues with large objects, notably their use of
OIDs. Lots of LOs can lead to OID depletion. There was a thread about
this recently.
It might be about time to come up with an extension that's a replacement
for large objects.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
What would it take to fund such an extension?
It would "have to" support:
- Migrate existing LOs away from pg_largeobject
- Proper driver-support (JDBC)
- Possible to exclude from pg_dump
- Support pg_upgrade
And -hackers should agree on the goal to ultimately being merged into core and
replace pg_largeobject.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Regina Obe | 2016-01-10 21:45:21 | Re: Code of Conduct: Is it time? |
Previous Message | Jim Nasby | 2016-01-10 21:38:05 | Re: Execute commands in single-user mode |