Nick Wellnhofer <[EMAIL PROTECTED]> writes:
> I found out that the process was looping in enlargeStringInfo() in
> backend/lib/stringinfo.c.
This problem was reported by someone else recently. I've just applied
the attached patch.
> The real cause of the problem seems to be a frontend/backend
Nick Wellnhofer <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Yeah, it kinda sounds like someone is trying to send an HTTP request to
>> the Postgres port :-(
> I thought about that, but I have TCP disabled. And it's definitely
> triggered by my own Perl code serving dynamic web pages. But it
Martin Pitt wrote:
> A week ago we at Debian received the bug report below: due to a
> buffer overflow in psqlodbc it is possible to crash (and possibly
> exploit) apache. I already sent this mail to the psqlodbc list [1],
> but unfortunately got no response so far. So maybe there are some
> hacker
Hi!
On 2004-05-12 1:31 +0200, Peter Eisentraut wrote:
> Martin Pitt wrote:
> > A week ago we at Debian received the bug report below: due to a
> > buffer overflow in psqlodbc it is possible to crash (and possibly
> > exploit) apache. I already sent this mail to the psqlodbc list [1],
> > but unfo
The following bug has been logged online:
Bug reference: 1152
Logged by: Daniel Ruoso
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Debian GNU/Linux sid
Description:Primary key not applied in inherited tables
Details:
Hi,
I have th
Hello
I need to solve checking varchar array. I can write
CHECK('aaa' = ALL(x)) -- x is array
but I can't CHECK(ALL(x) = '') or CHECK (ALL(x) ~ 'regex')
I know so I can write plpgsql function. I have question for hackers. Do
You plan better support for it?
Thank You
Pavel Stehule
---
The following bug has been logged online:
Bug reference: 1149
Logged by: Fabien COELHO
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.5 Dev
Operating system: Linux Debian
Description:server includes not installed by default
Details:
It seems that server
The following bug has been logged online:
Bug reference: 1150
Logged by: Fabien Coelho
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.5 Dev
Operating system: Linux
Description:grant options not properly checked
Details:
It seems that GRANT ALL ON SCHEMA
Hi PostgreSQL developers!
A week ago we at Debian received the bug report below: due to a buffer
overflow in psqlodbc it is possible to crash (and possibly exploit)
apache. I already sent this mail to the psqlodbc list [1], but
unfortunately got no response so far. So maybe there are some hackers
Pavel Stehule <[EMAIL PROTECTED]> writes:
> I need to solve checking varchar array. I can write
> CHECK('aaa' = ALL(x)) -- x is array
> but I can't CHECK(ALL(x) = '') or CHECK (ALL(x) ~ 'regex')
> I know so I can write plpgsql function. I have question for hackers. Do
> You plan better support
The following bug has been logged online:
Bug reference: 1151
Logged by: laurent faillie
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: HP-UX 11.00
Description:Initdb fails ...
Details:
Hi all,
I'm trying to upgrade my 7.3.4 database
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> It seems that GRANT ALL ON SCHEMA does not properly
> check for grantor rights.
What's happening is that pg_namespace_aclcheck() allows the operation
if you have GRANT OPTION for *any* of the rights to be granted. The
same problem exists for al
Fabien COELHO <[EMAIL PROTECTED]> writes:
> I'm not Peter, but I have an answer anyway: the standard says it should be
> narrowed.
Hmm, and also 12.2 says:
8) For every combination of and on O specified
in , if there is no corresponding privilege
descriptor in C
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> creating template1 database in /pg_database/database/base/1... ok
> initializing pg_shadow... ok
> enabling unlimited row size for system tables... ok
> initializing pg_depend... ok
> creating system views... ERROR: did not find '}' at end of in
--- Tom Lane <[EMAIL PROTECTED]> a écrit :
> > creating system views... ERROR: did not find '}'
> at end of input node
>
> Hmm. This would seem to indicate a mismatch between
> the nodeToString
> and stringToNode routines (outfuncs.c and
> readfuncs.c), which is
> something we don't normally
Fabien COELHO <[EMAIL PROTECTED]> writes:
> While browsing the Access Rules of ... it is unclear.
I generally find SQL92 easier to read than SQL99. In SQL92,
section 11.37 says
8) For every combination of and on O specified
in , if there is no corresponding privilege de-
Dear Tom,
> > It seems that GRANT ALL ON SCHEMA does not properly
> > check for grantor rights.
>
> What's happening is that pg_namespace_aclcheck() allows the operation
> if you have GRANT OPTION for *any* of the rights to be granted. The
> same problem exists for all object types.
I did not h
I have a database 'testdb' with two schemas: 'public' and edinburgh'.
Public is empty, everything is in 'edinburgh'.
DROP DATABASE testdb;
Database no longer appears in list of databases in cluster. So far, so good.
CREATE DATABASE testdb;
Database appears again. But so does the schema 'edinbu
Dear Tom,
> ...
> Note that says WARNING, not ERROR. So I guess what we need to do is
> narrow the privilege set and issue a warning message.
Yep.
> I think this also bears on the question that was raised before about
> whether REVOKE should raise an error if you don't have the right to
> revo
Dear Tom,
> section 11.37 says
>
> 8) For every combination of and on O specified
> in , if there is no corresponding privilege de-
> scriptor in the set of identified privilege descriptors, then a
> completion condition is raised: warning-privilege
Hi,
for some time a postgres process on one of our web servers repeatedly
gets into an infinite loop. This happens very rarely, about once in a
week. Today I installed gdb on the server to trace down the problem.
I found out that the process was looping in enlargeStringInfo() in
backend/lib/st
Fabien COELHO <[EMAIL PROTECTED]> writes:
> I do not understand it that way.
> (1) I think that the "General Rules" apply ONLY IF the "Access Rules" are
> already fulfilled, that is I MUST have the grant option of the rights
> before going there?!
I looked at this more carefully. In both
Rachel Willmer <[EMAIL PROTECTED]> writes:
> DROP DATABASE testdb;
> CREATE DATABASE testdb;
> Database appears again. But so does the schema 'edinburgh', all its
> tables, views, data, etc.
Sounds like you created all that stuff in template1, and so it's being
copied into the new database. Rea
23 matches
Mail list logo
