Re: Largeobject Access Controls (r2460) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Largeobject Access Controls (r2460)
Date
Msg-id 603c8f070912170616q4edca247qf49990550c148ad@mail.gmail.com
Whole thread Raw
In response to Re: Largeobject Access Controls (r2460)  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Largeobject Access Controls (r2460)  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
2009/12/17 Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>:
>
> Robert Haas <robertmhaas@gmail.com> wrote:
>
>> 2009/12/16 KaiGai Kohei <kaigai@ak.jp.nec.com>:
>> >>>> ? ?long desc: When turned on, privilege checks on large objects perform with
>> >>>> ? ? ? ? ? ? ? backward compatibility as 8.4.x or earlier releases.
>
>> Mostly English quality, but there are some other issues too.  Proposed
>> patch attached.
>
> I remember we had discussions about the version number, like
> "Don't use '8.5' because it might be released as '9.0'", no?

I chose to follow the style which Tom indicated that he preferred
here.  We don't use the phrase "8.4.x series" anywhere else in the
documentation, so this doesn't seem like a good time to start.  Tom or
I will go through and renumber everything if we end up renaming the
release to 9.0.

> Another comment is I'd like to keep <link linkend="catalog-pg-largeobject-metadata">
> for the first <structname>pg_largeobject</structname> in each topic.

Those two things aren't the same.  Perhaps you meant <link
linkend="catalog-pg-largeobject">? I'll tweak the pg_largeobject and
pg_largeobject_metadata sections to make sure each has a link to the
other and commit this.  I also found one more spelling mistake so I
will include that correction as well.

...Robert


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Update on true serializable techniques in MVCC
Next
From: Rod Taylor
Date:
Subject: NOT IN Doesn't use Anti Joins?