Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42626=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X6cba-0001Nz-5W
 for pgsql-admin@arkaria.postgresql.org; Mon, 14 Jul 2014 09:31:30 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42626=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X6cbZ-0002aG-MA
 for pgsql-admin@arkaria.postgresql.org; Mon, 14 Jul 2014 09:31:29 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <liuyuanyuangogo@gmail.com>)
 id 1X6cbY-0002a8-Ji
 for pgsql-admin@postgresql.org; Mon, 14 Jul 2014 09:31:28 +0000
Received: from mail-pd0-x232.google.com ([2607:f8b0:400e:c02::232])
 by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <liuyuanyuangogo@gmail.com>)
 id 1X6cbV-0004rw-B8
 for pgsql-admin@postgresql.org; Mon, 14 Jul 2014 09:31:26 +0000
Received: by mail-pd0-f178.google.com with SMTP id r10so4979590pdi.9
 for <pgsql-admin@postgresql.org>; Mon, 14 Jul 2014 02:31:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=from:to:cc:references:in-reply-to:subject:date:message-id
 :mime-version:content-type:thread-index:content-language;
 bh=JYB0kWVSlzh/E1gzrZ1snvYbn4rOQ4lV55vpgR1nuC8=;
 b=v4MRuw8URRkZiTgYLRuOnJsvzOLPkstgjSuva4uaOy8RL+V6PEJaf7BrTasxympPs1
 Isa6dSFxMgl7BwoahUIUoFkZpmwMZBysUNgZj2LlplbH6u5XrqAtaJoU2S+nZstfB3jD
 sp1qZuupxCpHuHskS6E1jL/Nei8N5eCSuqWjHhn8iCbaPNTtiblaxtm9/7qpFHo6deqy
 5AJHt59XhJpbTLChbEQRfAOOd3DSP7B1qwl0NSlFEhNPesbo0sKeETv6VF3hSkaQGksj
 BDT+myS226KJ6wKdJxNu+tEgoB6cagoyGlwWi7BkqpIm7q2ocrB3MMqn6RmxkvSMv3PP
 Mlmw==
X-Received: by 10.66.146.199 with SMTP id te7mr2289644pab.106.1405330283695;
 Mon, 14 Jul 2014 02:31:23 -0700 (PDT)
Received: from YuanyuanPC ([58.58.27.50])
 by mx.google.com with ESMTPSA id bm6sm13697988pdb.76.2014.07.14.02.31.11
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Mon, 14 Jul 2014 02:31:23 -0700 (PDT)
From: "liuyuanyuan" <liuyuanyuangogo@gmail.com>
To: "'Guillaume Lelarge'" <guillaume@lelarge.info>
Cc: <pgsql-admin@postgresql.org>
References: <01e701cf9f2b$408100c0$c1830240$@gmail.com>
 <CAECtzeXrh1z1-gC=uPM84ioRmKKNiesrENpWh11aq6emO6+Zmg@mail.gmail.com>
In-Reply-To: 
 <CAECtzeXrh1z1-gC=uPM84ioRmKKNiesrENpWh11aq6emO6+Zmg@mail.gmail.com>
Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D:_=5BADMIN=5D_sql_to_grant_privile?=
 =?UTF-8?Q?ge_on_sequence?=
Date: Mon, 14 Jul 2014 17:31:01 +0800
Message-ID: <020f01cf9f46$5fff2ec0$1ffd8c40$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0210_01CF9F89.6E235920"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQLSQsLCxr9MeHiHw6F8us7gR0MTZwIYLdyUmYlFpeA=
Content-Language: zh-cn
X-Pg-Spam-Score: -1.0 (-)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multipart message in MIME format.

------=_NextPart_000_0210_01CF9F89.6E235920
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Guillaume! Thanks for your reply !

=20

Now that, I got the reason.

I knew  GRANT ON TABLE still works for sequence, but I think use GRANT =
ON SEQUENCE

in pgAdmin3 of newer version maybe much better. Because GRANT ON =
SEQUENCE is more clear,

and maybe that=E2=80=99s why developers create this syntax especially =
for sequence.

That=E2=80=99s only a suggestion, looking forward to hearing from you =
later~~

=20

Regards !

Yours,

Jasmine

=20

=20

=E5=8F=91=E4=BB=B6=E4=BA=BA: Guillaume Lelarge =
[mailto:guillaume@lelarge.info]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2014=E5=B9=B47=E6=9C=8814=E6=97=A5 =
16:50
=E6=94=B6=E4=BB=B6=E4=BA=BA: liuyuanyuan
=E6=8A=84=E9=80=81: pgsql-admin@postgresql.org
=E4=B8=BB=E9=A2=98: Re: [ADMIN] sql to grant privilege on sequence

=20

Le 14 juil. 2014 08:20, "liuyuanyuan" <liuyuanyuangogo@gmail.com =
<mailto:liuyuanyuangogo@gmail.com> > a =C3=A9crit :
>
> Hi, Hackers!
>
> I got a question about sequence SQL of pgadmin3 , such as pgAdmin3 of =
PostgreSQL9.3.
>
> I found when I GRANT privilege on sequence by pgAdmin3 tool, =
it=E2=80=99s always show me sql like:
>
> GRANT SELECT, UPDATE ON TABLE sequence_name TO =E2=80=A6.
>
> Rather than:
>
> GRANT SELECT, UPDATE ON SEQUENCE sequence_name TO =E2=80=A6.
>
> =20
>
> For example:
>
> When I use pgAdmin3 TO create a sequence, I input SEQUENCE NAME =
=E2=80=93 seq1 ,and add privilege SELECT to public,
>
> Then the SQL shows: GRANT .. ON TABLE =E2=80=A6
>
> =20
>
> =20
>
> I checked the documentation of PostgreSQL 9.3 (see =
http://www.postgresql.org/docs/9.3/interactive/sql-grant.html),
>
> Then I know the privileges grant on sequence are only a part of that =
on table.
>
> Then I want to know, why to use GRANT ON TABLE ? why not to use GRANT =
ON SEQUENCE ?
>

Because that was the way to do it before 8.2 iirc. And it still works. =
Nevertheless I'll look into it.


------=_NextPart_000_0210_01CF9F89.6E235920
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91;
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:"\@=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:"Lucida Sans Unicode";
	panose-1:2 11 6 2 3 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.phonetic3
	{mso-style-name:phonetic3;
	font-family:"Lucida Sans Unicode","sans-serif";
	color:#666666;
	font-weight:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
Thanks Guillaume</span><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#434343'>!</span><span =
class=3Dphonetic3><span lang=3DEN-US style=3D'font-size:9.0pt'> =
</span></span><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
Thanks for your reply !<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
Now that, I got the reason.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
I knew=C2=A0 GRANT ON TABLE still works for sequence, but I think use =
GRANT ON SEQUENCE<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
 in pgAdmin3 of newer version maybe much better. Because GRANT ON =
SEQUENCE is more clear,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
 and maybe that=E2=80=99s why developers create this syntax =
especially</span><span lang=3DEN-US> for =
sequence.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
That=E2=80=99s only a suggestion, looking forward to hearing from you =
later~~<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
Regards !<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
Yours,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#434343'>=
Jasmine</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:11.0pt;font-family:"=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91=
","sans-serif"'>=E5=8F=91=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91=
","sans-serif"'> Guillaume Lelarge [mailto:guillaume@lelarge.info] =
<br></span><b><span =
style=3D'font-size:11.0pt;font-family:"=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91=
","sans-serif"'>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4<span =
lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91=
","sans-serif"'> 2014</span><span =
style=3D'font-size:11.0pt;font-family:"=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91=
","sans-serif"'>=E5=B9=B4<span lang=3DEN-US>7</span>=E6=9C=88<span =
lang=3DEN-US>14</span>=E6=97=A5<span lang=3DEN-US> =
16:50<br></span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> =
liuyuanyuan<br></span><b>=E6=8A=84=E9=80=81<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> =
pgsql-admin@postgresql.org<br></span><b>=E4=B8=BB=E9=A2=98<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> Re: [ADMIN] sql to grant =
privilege on sequence<o:p></o:p></span></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p><span lang=3DEN-US>Le 14 =
juil. 2014 08:20, &quot;liuyuanyuan&quot; &lt;<a =
href=3D"mailto:liuyuanyuangogo@gmail.com">liuyuanyuangogo@gmail.com</a>&g=
t; a =C3=A9crit :<br>&gt;<br>&gt; Hi, Hackers!<br>&gt;<br>&gt; I got a =
question about sequence SQL of pgadmin3 , such as pgAdmin3 of =
PostgreSQL9.3.<br>&gt;<br>&gt; I found when I GRANT privilege on =
sequence by pgAdmin3 tool, it=E2=80=99s always show me sql =
like:<br>&gt;<br>&gt; GRANT SELECT, UPDATE ON TABLE sequence_name TO =
=E2=80=A6.<br>&gt;<br>&gt; Rather than:<br>&gt;<br>&gt; GRANT SELECT, =
UPDATE ON SEQUENCE sequence_name TO =E2=80=A6.<br>&gt;<br>&gt; =
&nbsp;<br>&gt;<br>&gt; For example:<br>&gt;<br>&gt; When I use pgAdmin3 =
TO create a sequence, I input SEQUENCE NAME =E2=80=93 seq1 ,and add =
privilege SELECT to public,<br>&gt;<br>&gt; Then the SQL shows: GRANT .. =
ON TABLE =E2=80=A6<br>&gt;<br>&gt; &nbsp;<br>&gt;<br>&gt; =
&nbsp;<br>&gt;<br>&gt; I checked the documentation of PostgreSQL 9.3 =
(see <a =
href=3D"http://www.postgresql.org/docs/9.3/interactive/sql-grant.html">ht=
tp://www.postgresql.org/docs/9.3/interactive/sql-grant.html</a>),<br>&gt;=
<br>&gt; Then I know the privileges grant on sequence are only a part of =
that on table.<br>&gt;<br>&gt; Then I want to know, why to use GRANT ON =
TABLE ? why not to use GRANT ON SEQUENCE =
?<br>&gt;<o:p></o:p></span></p><p><span lang=3DEN-US>Because that was =
the way to do it before 8.2 iirc. And it still works. Nevertheless I'll =
look into it.<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0210_01CF9F89.6E235920--