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

Re: Largeobject Access Controls (r2460)

From: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Largeobject Access Controls (r2460)
Date: 2010-01-28 23:40:19
Message-ID: 4B622063.9030808@ak.jp.nec.com (view raw or flat)
Thread:
Lists: pgsql-hackers
(2010/01/28 18:21), Takahiro Itagaki wrote:
> 
> KaiGai Kohei<kaigai(at)ak(dot)jp(dot)nec(dot)com>  wrote:
> 
>> The attached patch uses one TOC entry for each blob objects.
> 
> When I'm testing the new patch, I found "ALTER LARGE OBJECT" command
> returns "ALTER LARGEOBJECT" tag. Should it be "ALTER LARGE(space)OBJECT"
> instead?  As I remember, we had decided not to use LARGEOBJECT
> (without a space) in user-visible messages, right?

Sorry, I left for fix this tag when I was pointed out LARGEOBJECT should
be LARGE(space)OBJECT.

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

Attachment: pgsql-fix-large_object-tag.patch
Description: application/octect-stream (520 bytes)

In response to

Responses

pgsql-hackers by date

Next:From: Ivan Sergio BorgonovoDate: 2010-01-29 00:00:26
Subject: returning array in a field together with other types
Previous:From: Peter EisentrautDate: 2010-01-28 23:22:03
Subject: Re: Review: Typed Table

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