| From: | Marc Balmer <marc(at)msys(dot)ch> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Referential integrity on large objects |
| Date: | 2016-11-09 22:05:48 |
| Message-ID: | etPan.58239f9e.327b23c6.1ae@msys.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am looking for ways to ensure referential integrity on large objects. Something like having a column myoid in a table that holds an oid of a large object, and which throws an error when the referenced large object should be unlinked. Like "myoid references pg_largeobject(loid)", which does not work right now, as foreign keys to catalogs are not supported.
Do you have any idea if this could be accomplished? Would it be complicated? Could it be realised as a sponsored development? If so, what would be the estimated effort/cost?
I'd be happy to get any hints at this.
- mb
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-11-09 22:15:45 | Re: Bug in comparison of empty jsonb arrays to scalars |
| Previous Message | Tom Lane | 2016-11-09 21:51:59 | Re: pgsql: pgbench: Allow the transaction log file prefix to be changed. |