From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
Cc: | alex2010 <alexeysedov1982(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: about lob(idea) |
Date: | 2015-05-27 10:02:41 |
Message-ID: | CAECtzeW4CtBWefgL+jHP7faHhAAVm5b-LoXavxMuUhqwNuE56g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-05-27 0:01 GMT+02:00 Martín Marqués <martin(at)2ndquadrant(dot)com>:
> El 25/05/15 a las 06:13, alex2010 escribió:
> > Maybe it makes sense to add ability to store large objects in the same
> table space as the table.
> > Or an opportunity - to specify table space for a large object.
> > Do you have anything in todolists about it?
>
> This is something which has popped up on me more than once when giving
> talks about storing files in PostgreSQL (last PgDay Argentina there was
> quite a debate about it, particularly when bringing up the bytea <-> LO
> comparison). The concerns the people exposed had different end goals.
>
> One of the main concerns was the fact that all LO live in a common
> catalog table (pg_largeobjects).
>
> If the LO were stored per-database, with a some alike schema as
> pg_largeobjects, then they could be placed on any tablespace available,
> and even get dumped on a normal DB dump, which makes administration much
> simpler.
>
>
I don't get it. They are already stored database per database. Each
database has its own pg_largeobjects catalog where all Large Objects for
this database are stored.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jordan Gigov | 2015-05-27 10:39:21 | Triggers on transaction? |
Previous Message | Naoya Anzai | 2015-05-27 08:13:22 | Re: why does txid_current() assign new transaction-id? |