sion 2 illustrates more or less the behavior I would have expected.
I've read again Section 7.8 about WITH queries, but I have not seen
anything that would disprove my expectation.
Am I wrong somewhere? Or is this a subtle bug?
--
Fabien.
test.sql
Description: application/sql
--
Sent
UPDATE TO ...
Where "INTERNAL" would tag foreign key stuff while "EXTERNAL" would be
only the user stuff.
I'm not sure it would not add to the confusion, though.
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Hello,
I can't start postgres anymore
When I try to start postgresql script I've the following error message in
the logfile :
###
DEBUG: database system was interrupted being in recovery at 2002-11-07
14:12:46 CET
This probably means that some data blocks are corrupted
and you w
not Peter, but I have an answer anyway: the standard says it should be
narrowed.
ISO/IEC 9075-2:2003 (E)
12.3
...
Syntax Rules
1) ALL PRIVILEGES is equivalent to the specification of all of the
privileges on for which the has grantable
privilege descriptors.
--
Fabien Coelho - [EMAIL PROTECTED]
-
d is missing in my version of the standard,
because otherwise I cannot really extract a semantics from access rule 1
case a in 12.7. Case b is much more explicit in my version for , you need a "WITH ADMIN OPTION".
If my guess is correct and that an access rule is violated, then this
e access
rules directly, so the general rules would apply on an empty set.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
`/tmp/': Operation not permitted
If you want to call that a "feature", I disagree without further strong
argument, and anyway the documentation should be clear about that.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
ue about it on -hackers.
Ok. Thanks.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ompliance for
> privileges otherwise ...
I think that if pg really sticks to the spec as I finally understand it
with your help, it would not be bad. I mean with both error (empty set in
grant or revoke) and warnings (non grantable parts for grant, non granted
parts for revoke).
T
r to reinstall if
s?he forgot it...
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
nition of an "identified" privilege (see my previous mail), I
finally think that the specs is ok and it just need to be implemented.
The bizarre would be more in the way that things are explained in the spec
than what is specified.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
-
s a summary, it is pretty subtle, especially as the standard
wording is contrived, and postgres does not do what should be done in a
lot of cases. There are also actual "security" bugs.
For the TODO, I would suggest something general:
- fix grant/revoke wrt SQL standard, val
ss ?).
Well, keeping this noise does not look attractive.
So I think that the sequence would be better, if possible.
Same for groups, BTW.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
be
referenced before posting a bug-report. Any hints?
simply follow "bug reporting guidelines" on http://www.postgresql.org/ ?
--
Fabien COELHO _ http://www.cri.ensmp.fr/~coelho _ [EMAIL PROTECTED]
CRI-ENSMP, 35, rue Saint-Honoré, 77305 Fontainebleau cedex, France
phone: (+33|
thing like select relname from pg_class where relacl similar to
'[0-9]+=' would be sufficient.
Yep. Not with this very regexpr (think of user "tp01"), but something
like that could work, indeed.
--
Fabien COELHO _ http://www.cri.ensmp.fr/~coelho _ [EMAIL PROTECTED]
CRI-EN
esysid FROM pg_user;
...
nobody | 2147483647
bla | -2147483648
Warf!
I think that what is practical is to iterate through the sequence if some
user already exists. Collisions are unlikely, so it would not be
expensive.
So the only problem is to implement system-wide "cluster&qu
t_sysid" user/group could store the next value in the relevant shared
relations.
This approach would be light weight from the implementation point of view.
Not very clean, but that would be easy and would not change much the
catalog.
--
Fabien Coelho - [EMAIL PROTECTED]
--
nce would be a big trouble, because create user
are not issued that often, and I would not expect them to appear within a
large transaction.
Anyway I'm planing to hace a look at the real thing first (shared seq).
So no worry, and thanks for your question.
--
Fabien Coelho - [EMAIL PROTECTED]
uld be kept:
- validate grant/revoke (error, warning, success0 wrt sql standard
I may be interested in implementing ROLEs someday, and such tests would be
welcome just to check that nothing is broken.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)
s wrong with
wishing better/full testing of postgresql data access controls and compare
the results with what is defined by the norm?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
grand "TODO" item;-)
IMHO, this should be a prerequisite to adding "roles".
Hace a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
nexistent users during time vacuum?
Although that could be done, I'm not sure I would like such a thing
to happen.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if
ith tricky cases. The
formula may be simplified, but all these cases must pass. Please keep
them.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/backend/utils/adt/timestamp.c.origFri Jun 4 15:50:58 2004
--- ./src/backend/utils/adt/time
*** [dbsize.o] Error 1
It seems that GetDatabasePath was updated, but not all its callers were
fixed.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I wanted to report a bug, but could not:
http://www.postgresql.org/bugform.html ("Report a bug" link from
postgresql main page) leads to:
"Not Found, The requested URL /bugform.php was not found on this server."
--
Fabien Coelho - [EMAIL PROTECTED]
--
offer tablespace size as well.
Ok. I must admit that I did not pay attention to the unapplied patches
queue.
Thanks,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
>
> was just looking at this this morning. is there anyway to change
> ownership of a schema? i couldn't find one and thought i'd ask before
> whacking on the system tables.
"ALTER SCHEMA foo OWNER TO bla" if you're a super user.
--
Fabien Co
7;;
Hope this help, have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
> > "ALTER SCHEMA foo OWNER TO bla" if you're a super user.
>
> And using 8.0... I saw that but was looking for a 7.4 solution...
Maybe: UPDATE pg_namespace SET nspowner= WHERE nspname='foo';
--
Fabien Coelho - [EMAIL PROTECTED]
---
alog.sum
pg_catalog.max
pg_catalog.min
...
However psql \da show all of them in pg_catalog, as expected.
I cannot see the difference in the initialization script to explain that.
Maybe something wrong with the regproc type?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of b
t, either,
> but regproc can't do anything about that. Cast to regprocedure if you
> want to see a more helpful display of the function.
Much better indeed.
Thanks a lot for the light. Have a nice day.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast
> Am Dienstag, 17. August 2004 14:26 schrieb Fabien COELHO:
> > The patch adds missing the "libpgport.a" file to the installation under
> > "install-all-headers". It is needed by some contribs. I install the
> > library in "pkglibdir", but I was
st.
The connection to the server was lost. Attempting reset: Failed.
@:
!>
then
psql> ALTER INDEX bla.t_pkey SET TABLESPACE pg_default;
ERROR: could not create relation 1663/19396/19473: File exists
So the state is pretty incoherent.
Well, I can still drop the database.
--
F
ld do it by default). Something like:
DECLARE CURSOR foo FOR your-select-query...;
FETCH FORWARD 10 FROM foo;
FETCH FORWARD 10 FROM foo;
FETCH FORWARD 10 FROM foo;
...
CLOSE foo;
Hope this help.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
g down the connection does not seem to
be the appropriate action anyway.
Have a nice day,
--
Fabien.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Dear debuggers,
I'd like to report the following "strange" behavior that I encountered
while trying (a bad idea, I know) to use a rule as a "poor man sql-trigger".
It seems that "on update do also" rules the new.* fields are evaluated
several times instead of being computed once, which is a bad id
between
beta3 and beta4, on a debian linux box under an intel architecture.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
st be C or PL*.
That could also be a candidate TODO, next to "improve the doc"?
Thanks for your answer,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
ehow it is nearly as great as promised, but nearly only.
Well, thanks for your comment,
--
Fabien.
---(end of broadcast)---
TIP 8: explain analyze is your friend
e indeed unique, possibly with some
escaping: '""."constraint_name"'. I'm not sure
about the possible consequences of changing the constraint names, but as
the information is a set of views on top of pg_catalog, there may be none.
--
Fabien.
--
Sent via pgsql-bug
ug".
So at least please fill in this as a "bug" somewhere, even if you do not
want to fix it.
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
.connamespace
JOIN pg_class c ON con.conrelid = c.oid
--
Fabien Coelho - CRI, Maths & Systèmes, MINES ParisTech
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
el that this may deserve a "test". Otherwise, ISTM that it is
a "bug" to be recorded somewhere.
Have a nice day,
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
tion schema is more to be useful (1)
than to look beautiful (2).
Another technical proposal, a little more subtle and with possible
underlying issues I cannot foresee: have the constraint_name be a "pair of
sql_identifiers".
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql
yzing other people's schemas. I cannot
ask all other people on the planet to rewrite their schemas, I pick them
as they are.
Could you register this "bug" somewhere please?
Thanks for your time.
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
t the
standard implementation would be okay, was a reasonnable choice, even if
proved wrong afterwards.
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
from the developers point of view.
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ill be fine from the developers point of
view.
--
Fabien.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
bug, because
the run is so short.
BTW, I'm planning to submit an enhancement patch to pgbench to improve
measurements, that will include moving the start time after the thread is
started, and possibly help getting more consistent figures.
--
Fabien.
--
Sent via pgsql-bugs mailing list (
49 matches
Mail list logo
