Re: [HACKERS] SELECT currval('SEQ') broken? - Mailing list pgsql-hackers

From Vadim B. Mikheev
Subject Re: [HACKERS] SELECT currval('SEQ') broken?
Date
Msg-id 34F4A76B.E83A08BD@sable.krasnoyarsk.su
Whole thread Raw
In response to SELECT currval('SEQ') broken?  ("Michael J. Rogan" <mrogan@fpelectronics.com>)
Responses Re: [HACKERS] SELECT currval('SEQ') broken?  (jwieck@debis.com (Jan Wieck))
Re: [HACKERS] SELECT currval('SEQ') broken?  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
Michael J. Rogan wrote:
>
> Hello
>
> I like the added security of 6.3 however how do you grant access to
> SELECT currval('SEQ') AS id
> I get a permission error on seq.currval?
>
> I figured out how to use CVSUP so I am grabbing the latest version.
>
> If this is fixed in it then great otherwise any ideas?

I don't remember - did we NO_ACCESS to a table for public
as default or not ?
If yes then you have to GRANT permissions on sequences...

Vadim

pgsql-hackers by date:

Previous
From: "Danny White"
Date:
Subject: unsubscribe
Next
From: "Vadim B. Mikheev"
Date:
Subject: mode of libs