"Brian Budnick" <[EMAIL PROTECTED]> writes:
> IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=144,
> permission=700
> This type of error is usually caused by an improper
> shared memory or System V IPC semaphore configuration.
It looks like you don't have shared-memory support
> Jerome ALET <[EMAIL PROTECTED]> writes:
> > Now suppose you define a rule to act differently on delete or update
>
> Hmm, that's the first good argument I've seen in this thread. An ON
> DELETE rule could possibly invoke processing quite different from an
> ON UPDATE rule, and in that case it
Jerome ALET <[EMAIL PROTECTED]> writes:
> Now suppose you define a rule to act differently on delete or update
Hmm, that's the first good argument I've seen in this thread. An ON
DELETE rule could possibly invoke processing quite different from an
ON UPDATE rule, and in that case it could make s
Dear PostgreSQL,
I recently just downloaded the PostgreSQL 7.0beta1 tar.gz file from your
server
and was unable to get it to work. I then downloaded the 7.0beta snapshot for
3/09/2000 and I everything seemed to work just fine as far as doing the
gmake,
gmake install, initdb. When I tried to run
> In a near future, I suppose you will allow acls to work on fields too.
> If you do it, you will notice that delete and update are really different in
> this case too.
>
> If you disagree with me, then document your "feature" and please stop wasting
> my time.
>
We are weighing the severity o
> On Thu, Mar 09, 2000 at 12:28:38PM -0500, Bruce Momjian wrote:
> > That is the issue? That UPDATE grants DELETE? I can UPDATE all fields
> > to NULL, and that is pretty much the same as DELETE. We can easily add
> > documentation on that "feature".
>
> Sure, do it, however you're still wrong
On Thu, Mar 09, 2000 at 12:28:38PM -0500, Bruce Momjian wrote:
> That is the issue? That UPDATE grants DELETE? I can UPDATE all fields
> to NULL, and that is pretty much the same as DELETE. We can easily add
> documentation on that "feature".
Sure, do it, however you're still wrong.
For the s
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> I'm fairly sure that lots and lots of people use postgresql, and very few
>> of them run 7.x, how many of them know that a grant update also grants
>> delete and vice-versa ?
> That is the issue? That UPDATE grants DELETE? I can UPDATE all fields
>
Kardos, Dr. Andreas writes:
> I have tested the pg_dumpall (with PATHNAME stuff) which Peter E. has mailed
> to this list.
>
> It works fine on QNX4 but definitly not on Digital Unix.
>
> The version in CVS works in general, but not on QNX4. On QNX4 I have to
> remove the escape backslashes.
O
> It seems we can't agree on this, because you postgresql hackers doesn't
> seem to understand what the problem is. I personnally can't understand why
> correcting a security problem would be a bad idea.
>
> As a developper myself, I perfecly understand your point of view on non
> doing major cha
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> Bruce Momjian writes:
>
> > > > 3. QNX4 only: The double quotes in
> > > >
> > > > POSTGRES_USER="`echo \" \
> > > >
> > > > etc. must not be escaped with a backslash.
> > >
> > > Technically, it should just work without them (the back
Your name : Pinaud Bruno
Your email address : [EMAIL PROTECTED] or [EMAIL PROTECTED]
System Configuration
-
Architecture : Pentium 3
Operating System : RedHat Linux 6.1
PostgreSQL version : PostgreSQL-7.0 Beta1
Compile
I have tested the pg_dumpall (with PATHNAME stuff) which Peter E. has mailed
to this list.
It works fine on QNX4 but definitly not on Digital Unix.
The version in CVS works in general, but not on QNX4. On QNX4 I have to
remove the escape backslashes.
Andreas Kardos
-Ursprüngliche Nachricht
libpq++ is not compilable on Digital Unix since the line
using namespace std;
has been included into interfaces/libpq++/pgconnection.h probably because of
Irix.
Andreas Kardos
14 matches
Mail list logo
