Re: Largeobject Access Controls (r2460)

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>

Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>, Robert Haas <robertmhaas@gmail.com>, KaiGai Kohei <kaigai@ak.jp.nec.com>, Tom Lane <tgl@sss.pgh.pa.us>, Jaime Casanova <jcasanov@systemguards.com.ec>, Greg Smith <greg@2ndquadrant.com>, pgsql-hackers@postgresql.org

Date: 2010-02-08T13:23:11Z

Lists: pgsql-hackers

Takahiro Itagaki escribió:
> 
> KaiGai Kohei <kaigai@kaigai.gr.jp> wrote:
> 
> > > 	default:	both contents and metadata
> > > 	--data-only:	same
> > > 	--schema-only:	neither
> > 
> > However, it means only large object performs an exceptional object class
> > that dumps its owner, acl and comment even if --data-only is given.
> > Is it really what you suggested, isn't it?
> 
> I wonder we still need to have both "BLOB ITEM" and "BLOB DATA"
> even if we will take the all-or-nothing behavior. Can we handle
> BLOB's owner, acl, comment and data with one entry kind?

I don't think this is necessarily a good idea.  We might decide to treat
both things separately in the future and it having them represented
separately in the dump would prove useful.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.