Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] [v8.5] Security checks on largeobjects

From: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] [v8.5] Security checks on largeobjects
Date: 2009-06-28 23:32:29
Message-ID: 4A47FD8D.8090705@ak.jp.nec.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Bernd Helmle wrote:
> --On 26. Juni 2009 13:08:37 +0900 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> 
> wrote:
> 
>>  * Is the named large object (including fully qualified one) worth?
>>    It will enables us to specify a largeobject with human readable
>>    identifier string.
> 
> I don't understand the notion of this. Does this mean you can create a 
> LO with an identifier string, generated from (e.g.) your application?

Yes, it intends to assign an identifier string not only numeric
large object identifier. The identifier string can be qualified
with a certain namespace as follows.

E.g)
 SELECT lo_open('my_picture01', x'40000'::int);
 SELECT lo_create('pg_temp.my_musid02');

In the later case, the new largeobject will be reclaimed after
the session closed due to the temporary namespace.

Thanks,
-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-06-29 02:41:57
Subject: Re: dependencies for generated header files
Previous:From: David FetterDate: 2009-06-28 22:35:38
Subject: Re: pre-proposal: permissions made easier

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group