Developer's FAQ updated to:
palloc() and pfree() are used in place of malloc()
and free() because we find it easier to automatically free all
memory allocated when a query completes. This assures us that all
memory that was allocated gets freed even if we have lost track of
w
Tom Lane wrote:
> What would you have it do differently? Accept the insert and then give
> some random error message at the commit? I'm sorry, but I don't see
> a problem here.
> regards, tom lane
Thanks Tom
I would like to see error message 'ERROR: Can't serialize acce
Hi,
I am running 7.2b3 and trying to make something like this work (new
refcursor stuff):
CREATE TABLE t (c text);
CREATE FUNCTION errtest(refcursor, text) RETURNS refcursor AS '
BEGIN
OPEN $1 FOR SELECT c FROM t WHERE c=$2;
RETURN $1;
END;
' LANGUAGE 'plpgsql';
INSERT INTO t V
pl/tcl language not install cygwin
--
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Shahid Mohammad Shamsi ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
select table privilege in postgres allows user to create index on the table
Long Description
I created a user and assigned select privilege on a table. The
Shahid Mohammad Shamsi ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
select table privilege in postgres allows user to create index on the table
Long Description
I created a user and assigned select privilege on a table. The
[EMAIL PROTECTED] writes:
> select table privilege in postgres allows user to create index on the table
Actually, it appears that CREATE INDEX has no permission check at all.
I agree this is a bug. Probably CREATE INDEX should require ownership
permission, the same as ALTER TABLE.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO:
> * Allow only owner to create indexes
I was going to just fix it now. Do you want to leave it for 7.3?
regards, tom lane
---(end of broadcast)---
TIP 5: Hav
Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > select table privilege in postgres allows user to create index on the table
>
> Actually, it appears that CREATE INDEX has no permission check at all.
>
> I agree this is a bug. Probably CREATE INDEX should require ownership
> permission, the sam
Hi,
I created a user and assigned select privilege on a table. The user can not
insert any data or add a field to the table. But, the user can create
indexes on the table despite having select only privileges. This becomes a
serious problem if the user can create unique indexes on the table where
Dmitry Fomichev <[EMAIL PROTECTED]> writes:
> I am running 7.2b3 and trying to make something like this work (new
> refcursor stuff):
> CREATE TABLE t (c text);
> CREATE FUNCTION errtest(refcursor, text) RETURNS refcursor AS '
> BEGIN
> OPEN $1 FOR SELECT c FROM t WHERE c=$2;
> R
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Added to TODO:
> > * Allow only owner to create indexes
>
> I was going to just fix it now. Do you want to leave it for 7.3?
If you think it is safe, go ahead. I fixed some stuff last night. :-)
I will remove from TODO when
12 matches
Mail list logo
