On Wed, 2 Jul 2003, Jodi Kanter wrote:
> The following comment can be seen on the main postgres page which
> discusses the new 7.3.3 release. Can someone tell me more about the
> reference to timestamptz_izone? Or is there a doc that will detail more
> about it? I want to make sure that we do not
Title:
The following comment can be seen on the main postgres page which discusses
the new 7.3.3 release. Can someone tell me more about the reference to timestamptz_izone?
Or is there a doc that will detail more about it? I want to make sure that
we do not need
Set the function to run as SECURITY DEFINER
The owner/creator of the function must have the privileges to insert data into
the fore mentioned tables and it should do as you asked.
This feature is only available in 7.3 and above.
Regards
Donald Fraser
- Original Message -
From: "Kris Kiger
Kris Kiger <[EMAIL PROTECTED]> writes:
> Here's my problem. I have user X calling a database function. The
> function inserts data into table Y. User X only has select access to
> this table. Is there some way to allow user X to call a function that
> does an insert for him/her without user
Kris Kiger wrote:
Here's my problem. I have user X calling a database function. The
function inserts data into table Y. User X only has select access to
this table. Is there some way to allow user X to call a function that
does an insert for him/her without user X having to have write access
Here's my problem. I have user X calling a database function. The
function inserts data into table Y. User X only has select access to
this table. Is there some way to allow user X to call a function that
does an insert for him/her without user X having to have write access to
table Y? Is
Hello Scott,
> Note that even if you ARE going to run each cluster under a different user
> (I recommend running each cluster under a different user so you can do
> 'insane' things like let each person have C as an untrusted language and
> be their own superuser in a mostly sane way) you still only
Derek Main <[EMAIL PROTECTED]> writes:
> [ pg_dump works as root, fails as postgres ]
> I have since found that this is not caused by a space problem since the
> last time I ran the command, only 90% of the disk was used when it
> crashed.
I think you've forgotten a standard Unix behavior: root
This is getting stranger. If I login as 'root' and run the following command
:
/bin/su postgres -c "/usr/local/pgsql/bin/pg_dump -Ft > /tmp/dbase.backup.tar
; echo $? > /tmp/errfile"
then errfile contains a return code of 0 (zero).
If I login as 'postgres' and run the following com
Ian Barwick <[EMAIL PROTECTED]> writes:
> You only need to compile PostgreSQL once (e.g. with
> --prefix=/usr/local/pgsql-733); by supplying different data directories and
> logfiles etc. on server start you can run multiple instances simultaneously
> under the same system user.
Or different users
On Wed, 2 Jul 2003, Ian Barwick wrote:
> On Wednesday 02 July 2003 09:18, Daniel Seichter wrote:
> > Hello,
> > I want to discuss a little bit about the following situation:
> > I only have one server for my databases.I had to develope on this server
> > and also had to manage several databases, s
On Wednesday 02 July 2003 09:18, Daniel Seichter wrote:
> Hello,
> I want to discuss a little bit about the following situation:
> I only have one server for my databases.I had to develope on this server
> and also had to manage several databases, so I can expect problems if I had
> to restart post
Hello,
I want to discuss a little bit about the following situation:
I only have one server for my databases.I had to develope on this server and
also had to manage several databases, so I can expect problems if I had to
restart postgreSQL, if I changed the logging.
What do you think about this
13 matches
Mail list logo
